docs: add registry anchoring and audit chain verification tutorials#62
Merged
Conversation
Two new tutorials filling gaps identified in the tutorial coverage audit: - anchoring-to-the-registry.md: how to set the transparency field via direct SCITT HTTP submission (no SDK registry client exists yet); explains the pending-placeholder pattern for dev, re-sign after anchoring, and what verification step 6 requires of a verifier - verifying-the-audit-chain.md: how to verify tool_transcript.hash against the external transcript bytes, validate call count, and understand external execution receipts per spec §3.3.1 mkdocs.yml: adds both tutorials to the Tutorials nav Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
transparencyfield end-to-end — dev placeholder pattern, SCITT HTTP submission (no SDK client yet, noted explicitly), re-signing with the real receipt URI, and what verification step 6 checkstool_transcripthash verification against raw transcript bytes, call count cross-check, and external execution receipts per spec §3.3.1Both tutorials are grounded in the actual
TrustRecordandToolTranscriptmodels — no invented SDK APIs.Test plan
mkdocs serverenders both tutorials under Tutorials nav without errorsagentrust_trace.sign,hashlib,json,requests)sha256:andsha384:prefixes"pending") documented with production warning🤖 Generated with Claude Code