Repository navigation
Tooling: require complete receipts in public frontier verification - #847
Merged
Mister-Meeseeks merged 1 commit intoOct 13, 2026
Merged
Mister-Meeseeks merged 1 commit into
Mister-Meeseeks merged 1 commit into
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.
The public PR741/PR799 verification commands now require the complete PR741 replay receipt before accepting reused ancestry or publishing success. This follows Lucas (@ljste)'s finding in #838 at
2a50020bb9564229874cbfbdc112e17b235bacfc: the historical checker accepts a replaced stage or missing artifact when its receipt is changed consistently. Tooling integration; no new κ and no independent-discovery claim.A new entrypoint requires all 22 ordered stages, all 44 artifact paths and agreement with
STAGES.json, then retains every historical composition check. Both Make targets and both cold-replay workflows use it. The old verifiers are hash-pinned proof supplements, so their bytes, selected records and source packages remain untouched. Historical output is kept underwork/replay/; onlywork/RESULT.jsonrecords successful completion of the new entrypoint.Validation on isolated Linux CPython 3.12.15:
python3 -B -m unittest discover -s tests -p 'test_frontier_replay_coverage.py' -v make frontier799-verifyFresh full cold replay and hosted CI are not claimed as locally completed. Both updated CI workflows retain the full cold replay. The coverage gate detects omissions; it does not authenticate fabricated logs, audit every #799 obligation, or prove the multiplication theorem. The inherited mathematical assumptions and selected bound are unchanged.
Base:
f567884aeb8851b6e794af1184119a3bfbe1e631. Implementation, output layout and scope. Credit Lucas for #838; Douglas Colkitt for the checkers/replays; Chafik Boukhalfa for #741; DreamingOfClouds and eumemic for the #589/#555 lineage. Integration by Chinmay (@chinmayarvind23), with substantial OpenAI Codex assistance, under Apache-2.0.