Skip to content

The 1 November packet, corrected where its own records contradicted its wording - #42

Merged
chrisjleal merged 1 commit into
mainfrom
docs/nov01-correction
Nov 2, 2026
Merged

chrisjleal merged 1 commit into
mainfrom
docs/nov01-correction

Conversation

@chrisjleal

Copy link
Copy Markdown
Contributor

A correction revision of 2026-11-01-suite, which stays published and byte-identical at 9358761.

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.json and authority-effect-results.json are byte-identical between the two packets. CORRECTION.md lists every payload hash before and after.

What moved, and why it had to:

  1. manifest.json → grading_scope.binding now states what observed_matches_expected grades: the authority predicate of each case with the typed boundary capture for post_dispatch_revoke. Previously the flag passed while the trace's expectation required a committed, read-back effect — a fitted reading.
  2. manifest.json → post_dispatch_revocation.separates no 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).
  3. trace.jsonl carries the expectation the run was appraised against, marked expectation_status: superseded_by_revision with expectation_revised, rather than silently matching a sentence the run contradicts. The packet names the packet it corrects through supersedes and correction.

Also fixes a reader-facing defect found while checking this: reproduce/aad.mjs verify and report only understood the October packet shape and crashed on both November packets (manifest.delegationRoot against 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 FAIL when 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 -c on both packets, the corrected packet's own node verify-portable-proofs.mjs as a reader runs it, verify-reader-checks.mjs 0 failures, node aad.mjs verify and report on all three packets (November corrected, November original, October), markdownlint 0 errors.

…ts wording; the kit verifies both packet shapes
@chrisjleal
chrisjleal merged commit 35568cb into main Nov 2, 2026
2 checks passed
@chrisjleal
chrisjleal deleted the docs/nov01-correction branch November 2, 2026 05:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant