Repository navigation
Bind action receipts to a monotonic host policy epoch - #466
Merged
Merged
Conversation
aruintelligence
force-pushed
the
codex/policy-epoch-receipts
branch
from
October 20, 2026 05:45
96fab32 to
aab770d
Compare
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
policyEpoch()to the four receipt-bound adapters. Its nonnegative safe integer is included in the signed receipt and rechecked after approval and before dispatch. A change or unavailable value suppresses dispatch and spends the grant; integrations without the option keep their receipt format.Verification
npm test: 1,090 passed, 0 failedbash reproduction/action-boundary/reproduce.sh: passednode scripts/verify-action-receipt-registry.mjs --check --append-only-base HEADbefore commit: 508 entries, previous 504 unchangednpm run check:links: 423 Markdown files passedgit diff --check: cleanThe epoch comparison uses in-memory host state and local callbacks. A production host must persist a monotonic epoch and increment it for policy and destination-mapping changes; this change does not prove that external behavior.