docs: clarify action receipt verification boundary - #92
Merged
imran-siddique merged 1 commit intoJul 7, 2026
Merged
Conversation
Signed-off-by: Carlos Hernandez-Vaquero <carloshvp@gmail.com>
imran-siddique
approved these changes
Jul 7, 2026
imran-siddique
left a comment
Contributor
There was a problem hiding this comment.
Approving. The new §3.3.2 (informative) and the verification-guide additions are accurate and well-scoped.
- Purely informative and additive: no change to
schema/trace-claim.json, and the newexamples/action-receipts/fixtures are explicitly marked as non-Trust-Records not validated by the schema (examples/README.md+examples/action-receipts/README.md), soadditionalProperties: falseis not at risk. - The verification boundary is stated correctly and consistently with the existing §3.3.1 trust-boundary paragraph: a signed controller rejection is valid negative evidence, not a TRACE verification failure, while a signed acceptance does not prove physical completion or functional-safety certification unless a stricter profile defines and trusts that external claim. The four outcomes (
receipt_valid_accepted/receipt_valid_rejected/receipt_missing_required/receipt_invalid) are coherent and match between spec, verification.md, and the fixture README. - Correctly keeps the action-receipt requirement axis independent of build-provenance depth, and the verifier steps (recompute digest, trusted issuer key not the embedded key, chain ordering, session/call binding, report missing/stale separately) mirror the §3.3.1 rules.
CI green. LGTM.
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
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
Refs #66.
Validation
.venv/bin/ruff check src tests.venv/bin/mypy src/agentrust_trace.venv/bin/pytest --cov=agentrust_trace --cov-report=term-missinggit diff --checkDocs build note:
.venv/bin/mkdocs build --strict --site-dir /tmp/trace-action-receipts-site-checkcurrently fails before rendering changed pages because the existing MkDocs config usesdocs_dir: ., which MkDocs rejects as the parent directory of the config file.