docs: check the shared platform-state caveat against trace-spec - #126
Merged
Conversation
The SEV-SNP platform-state caveat here is verbatim with trace-spec and cmcp apart from one sentence. Nothing linked the three, so a change in one, such as agent-manifest shipping appraise_platform_info() on 2026-08-20, reaches the others only if someone remembers. - Wraps the shared prose in shared:platform-state-appraisal markers and moves the cA2A-specific sentence below the end marker, including the detail that neither the attested-peer nor the sealed-channel path calls the appraisal. - Adds a limitations-parity workflow that fetches trace-spec's copy and fails on drift, on push, on PR and daily. Same shape as the schema-parity check on the apex site. Only the marked block is compared; the paragraph after it is this project's own. The full text stays here rather than becoming a link. LIMITATIONS.md exists to state the bounds where a reader meets them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013EQx4N5BzTQbY8kvXUsdkY
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.
Follow-up to trace-spec#195, which is merged.
The SEV-SNP platform-state caveat in
LIMITATIONS.mdis verbatim with trace-spec and cmcp apart from one sentence. Nothing linked the three, so a change in one reaches the others only if someone remembers.agent-manifestshippingappraise_platform_info()on 2026-08-20 is exactly that kind of change.What this does
<!-- shared:platform-state-appraisal begin/end -->markers and moves the cA2A-specific sentence below the end marker as an In cA2A paragraph, keeping the detail that neither the attested-peer nor the sealed-channel path calls the appraisal.limitations-parity.yml, which fetches trace-spec's copy and fails on drift, on push, on PR and daily at 06:41. Same shape as theschema-paritycheck on the apex site. Only the marked block is compared; the paragraph after it is this project's own and is free to differ.The full text stays here rather than becoming a link to trace-spec.
LIMITATIONS.mdexists to state the bounds where a reader will actually meet them, so this keeps the copies honest instead of thinning them out.Builds clean under
mkdocs build --strict. Parity extraction was tested locally against trace-specmain, including a negative case that confirms drift is caught.🤖 Generated with Claude Code
https://claude.ai/code/session_013EQx4N5BzTQbY8kvXUsdkY