Skip to content

Say why the two witness fields cannot move for the September 7 capture - #59

Merged
imran-siddique merged 1 commit into
mainfrom
docs/registry-witness-fields-per-receipt
Sep 11, 2026
Merged

Say why the two witness fields cannot move for the September 7 capture#59
imran-siddique merged 1 commit into
mainfrom
docs/registry-witness-fields-per-receipt

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

The registry page reported witness_time_established and grade_cryptographically_bound as false for the September 7 capture without saying why they stay false, which reads as a line with a shelf life once the witness operator ships support for the two fields.

The witness signature covers the protected header the fields are read from, so a receipt carrying a CWT iat or a signed grade is a separately signed receipt. That receipt's header decodes to {1: -8, 395: 1}, algorithm and tree profile only.

Stated that way the line needs no pass at deploy time.

Matches agentrust-io/trace-registry#72, which makes the same correction in the README, LIMITATIONS and the evidence packet.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DLHonYjqypEL2Zjd8VGmb6

…ptember 7 capture

The page reported witness_time_established and grade_cryptographically_bound as
false for that capture without saying why they stay false. The witness signature
covers the protected header the fields are read from, so a receipt carrying a CWT
iat or a signed grade is a separately signed receipt. A witness shipping support
for them changes a later receipt and leaves the archived one alone.

Stated that way the line has no shelf life and needs no pass at deploy time.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DLHonYjqypEL2Zjd8VGmb6
@imran-siddique
imran-siddique merged commit 2318848 into main Sep 11, 2026
4 checks passed
@imran-siddique
imran-siddique deleted the docs/registry-witness-fields-per-receipt branch September 11, 2026 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant