Repository navigation
Publish append-only action receipt registry with one-command verifier - #459
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
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.
Indexes 121 distinct receipts in a Git-based, hash-chained JSONL registry: 100 project-authored simulated challenge cases, one observed Chrome matrix run, ten controlled site host dispatches, and ten paired live browser pilot receipts. Each entry binds a full source-file SHA-256, record location, receipt hash and previous entry hash. The source manifest is append-only, and CI rejects edits/deletions relative to the parent commit.
node scripts/verify-action-receipt-registry.mjs --checkrecomputes the chain and all receipt hashes, then replays the challenge in JavaScript and Python and verifies the browser observation plus ten paired source, DOM, and screenshot artifacts.Registry SHA-256:
bb1ae15f23de176f72e3aa9f6e77da86bd2639103c6fb0b75785ba2748c0d564. Chain root:35beb7fcf32e724ddd13744f4f2e68e6838e2878e9d33cffde01c5d9c0ebb191.No independent outside validation is claimed; the registry's Git history exposes later edits but does not authenticate the actor or prove external side-effect completion.