docs: say the suite checks attestation field shape, not the attestation - #110
Merged
Conversation
The metadata said the suite checks that attestation receipts satisfy the specification before shipping to production, and levels.md called Level 1 production TEE-attested records. LIMITATIONS.md says TR-RTE checks the shape of the attestation fields, not the attestation. The metadata, README heading and both level tables now say what the suite checks. Also: index.md said eight modules and listed seven; TR-APR is added. The README said test suite v0.2 while the package is 0.5.1; it now only states the spec version it tracks. The site description and footer lose their em dashes, doc samples use a placeholder model, and SPONSORS.md names OPAQUE as sponsor without the disclaimer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013aK3gVWzNdcM3hZ2o2awK2
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 site metadata said the suite checks "that your attestation receipts satisfy the specification ... before shipping them to production", and levels.md called Level 1 "Production TEE-attested records". LIMITATIONS.md says TR-RTE checks the shape of the attestation fields, not the attestation. The llms.txt description, the JSON-LD, the index description, the README heading and both level tables now say what the suite actually checks.
Also in this PR
example-providerandexample-model-1.Left alone on purpose: test vectors keep their model fields, and the em dashes in module page headings are a separate style pass.
Checked: tests/test_docs_match_the_modules.py passes (6 of 6) in a clean venv with this tree installed editable; mkdocs.yml parses in both its committed form and the deploy's docs_dir rewrite.
Generated with Claude Code
https://claude.ai/code/session_013aK3gVWzNdcM3hZ2o2awK2