Skip to main content

​
Correction to 2026-11-01-suite

This directory corrects the packet at ../2026-11-01-suite/ — 2026-11-01-suite@9358761ff88444425b85fc77266609916de4c16b. No evidence was re-run and no record changed. The run, the revision, the job and authority records and every disclosed envelope are those of aad-2026-11-01T22-24-26-865Z on 0d1b934f40d38233fa588267354fcccec5e1edeb. This revision corrects wording and grading scope, and is identified separately so that a reader can tell a correction from a new evaluation. The packet it corrects stays published and hash-pinned.

​
What changed

  1. manifest.json → grading_scope.binding states what observed_matches_expected grades: the authority predicate of each case together with the typed boundary capture for post_dispatch_revoke. It does not grade the literal committed-effect clause of the expectation as first written.
  2. manifest.json → post_dispatch_revocation.separates no longer describes the earlier action as already committed. It states the boundary outcome this run recorded (refused_at_tool_call).
  3. trace.jsonl → the post_dispatch_revoke record carries expectation_status: superseded_by_revision and expectation_revised, so the expectation the run was appraised against is retained and marked rather than silently matched.

​
What each payload hash covers

Verify both: sha256sum -c SHA256SUMS here, and the same command in ../2026-11-01-suite/, which is unchanged.
Last modified on November 2, 2026