Repository navigation
Require audit and attention evidence in verified receipts - #364
Merged
Merged
Conversation
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.
Change
Reproduction and proof
Before this change, deleting either artifact and recalculating the receipt hash left
verifyExecutionReceipt(...).verifiedtrue andsignExecutionReceiptsigned it. Replacing auditentrieswith an empty string, recalculating audit/receipt hashes, also passed signing. The Python capsule verifier rejected all three shapes.The regression tests now reject those cases. Three additional cross-runtime capsule fixtures recalculate the outer capsule digests and Ed25519 receipt signatures; JavaScript and Python both reject all three. Local checks: 808 Node tests, 42 capsule cases, 28 HTTP exchange cases, 13 enterprise pilot cases, installed-package compatibility, API and upgrade contract checks, and Markdown links.
This checks presence and structure of these artifacts, not the truth of declared intent, policy correctness, or whether a real user saw the rendered output. The checks are project-authored.