content(registry): the witness deploy does not reach the September 7 capture - #60
Merged
Merged
Conversation
…capture The page said both fields stay false for that capture because the signature covers the header, which is true and is the weaker reason. The witness deployed iat and grade signing on September 12 and confirmed that /checkpoints deduplicates on a content-addressed entry hash, so checkpoint 1 cannot be re-submitted for a new receipt at all, and because that hash is derived from the signed fields rather than the submitted bytes, reformatting does not produce a new one either. A receipt carrying a witness time needs a checkpoint the witness has not seen. This is the page the witness operator flagged as the one that would go stale at deploy time, since the sentence lives here rather than in the repo README. It now matches trace-registry LIMITATIONS.md (#77, #78). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X2GDChXjA7BAdDNzCAmBJv
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The witness operator flagged this page back on September 9 as the one that would go stale at deploy time, because the sentence about the two fields lives here rather than in the repo README that #72 fixed.
The deploy happened on September 12, and the page needed a change after all, though not the one either of us expected. It said both fields stay false for the September 7 capture because the witness signature covers the header. True, and the weaker reason.
The stronger one:
/checkpointsdeduplicates on a content-addressed entry hash, so checkpoint 1 cannot be re-submitted for a new receipt at all. And because that hash is derived from the signed fields rather than the submitted bytes, reformatting the submission does not produce a new one either. A receipt carrying a witness time therefore requires a checkpoint the witness has not seen.Now matches trace-registry
LIMITATIONS.md(#77, #78). One paragraph, no layout or structural change.🤖 Generated with Claude Code
https://claude.ai/code/session_01X2GDChXjA7BAdDNzCAmBJv