Repository navigation
The 1 November packet, corrected where its own records contradicted its wording - #42
Merged
Merged
Conversation
…ts wording; the kit verifies both packet shapes
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.
A correction revision of
2026-11-01-suite, which stays published and byte-identical at9358761.No evidence was re-run and no record changed. Same run (
aad-2026-11-01T22-24-26-865Z), same revision (0d1b934f4…), same job and authority records, the same 15 disclosed envelopes —portable-proofs.jsonandauthority-effect-results.jsonare byte-identical between the two packets.CORRECTION.mdlists every payload hash before and after.What moved, and why it had to:
manifest.json → grading_scope.bindingnow states whatobserved_matches_expectedgrades: the authority predicate of each case with the typed boundary capture forpost_dispatch_revoke. Previously the flag passed while the trace's expectation required a committed, read-back effect — a fitted reading.manifest.json → post_dispatch_revocation.separatesno longer describes the earlier action as already committed. It states the outcome this run recorded (refused_at_tool_call: the executor re-read authority at its own boundary and refused the call).trace.jsonlcarries the expectation the run was appraised against, markedexpectation_status: superseded_by_revisionwithexpectation_revised, rather than silently matching a sentence the run contradicts. The packet names the packet it corrects throughsupersedesandcorrection.Also fixes a reader-facing defect found while checking this:
reproduce/aad.mjs verifyandreportonly understood the October packet shape and crashed on both November packets (manifest.delegationRootagainst a v3 manifest). They now detect the packet shape by content and verify the v3 shape — checksums, the trace digest the manifest claims, every envelope offline, and the declared coverage (coverage FAILwhen a case is missing, because a missing case is not a passing case) — and print typed cost and grading scope. The October shape still verifies unchanged.Verified locally:
sha256sum -con both packets, the corrected packet's ownnode verify-portable-proofs.mjsas a reader runs it,verify-reader-checks.mjs0 failures,node aad.mjs verifyandreporton all three packets (November corrected, November original, October), markdownlint 0 errors.