Phase 2: seal and replay outcome-independent intent tapes #648
No reviewers
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erikinkinen/AES!648
Loading…
Reference in a new issue
No description provided.
Delete branch "phase2/p2-09-immutable-intent-tapes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task
Closes #100 (P2-09).
Summary
An expected denial can change a mechanism's graph and event count. The new
immutable intent tapes keep the already generated source continuation identical
across those outcomes. Logical handles resolve through engine-owned reservations,
and every source action has an auditable range of actual v4 execution events.
Scope
Included
draw provenance, logical dispatcher and immutable initialized prefixes.
shared bounded zstd transport preserves existing event replay behavior.
denials, exact full/resumed replay, independent codec/schema/RNG/artifact checks,
documentation and hashed acceptance evidence.
Explicitly excluded
backlog leaves. These tests are implementation fixtures.
accelerate offline replay; the requested csaI Phase 5 supplement remains due.
Design intent
Seal and validate the entire tape before execution. Expose no mutable byte,
entry or RNG state. Bind the prefix to that tape, then stage copies for the
continuation. Preserve actual engine allocations even when issuance is denied;
missing parents cannot create authority. Policy/query expansion records actual
events without affecting the common source suffix or sampling future choices.
Archive whole-tape and continuation identities separately. A compressed reader
returns a sealed artifact only after framing, identity and complete tape
validation. It materializes the full tape and must discard partial failed writes.
Expected hashes establish manifest provenance when supplied; self-hashes alone
do not. The event transport extraction retains its prior reference fingerprint.
Phase discipline
Protocol 2.2 / backlog 2.2.1; Phase 2 only. The accepted schema-terminator bug
found during this work was filed separately as #646 and merged in #647; that
signed fix is integrated here. Frozen historical fixtures and protocol identities
remain intact.
Verification
37ff6e476884f4b162a35eba8e5fb09c1ab4cf15in Debug, Release and ClangASan/UBSan, with no skips. All eight repository hooks passed.
accepted 35 cases and rejected 31 malformed stream/identity cases per build.
complete event streams and 56 checkpoints. Both reference fingerprints agree
across all three configurations; the existing event fingerprint is unchanged.
corruption/schema regression tests passed. The frozen workspace scope passed.
Tracked acceptance records are under
artifacts/backlog/2.2.1/P2-09/.The issue's three checklist steps will be checked once after all eight checks
pass on the final PR head, immediately before the guarded fast-forward merge.
CI integration
The first PR head's two sanitizer jobs hit the 15-minute overall deadline after
80 passing tests; neither had an assertion failure. #649 / #650 preserves the
failure evidence and raises the bounded job budget while retaining the full
suite and 120-second per-test limit.
Signed integration head
4838e393be82ddb58f930d2244b479baa78eec45includes that fix. Every implementation,test, schema and build-target file is byte-identical to validated source
37ff6e476884f4b162a35eba8e5fb09c1ab4cf15; all 25 acceptance output hashes stillmatch. The only additions relative to that source are the two original acceptance
records and the CI budget/documentation change. The existing three complete local
suite runs remain exact-source evidence; no redundant new local simulator run is
claimed. All hooks and the frozen workspace scope pass on the integrated head.
Integration identity and verification evidence, SHA-256
9ce938b3af99ca0e2ac18bbccece16d66a8c040e069dc2ca64c053648c361cb2. All eight final-head remote checks are required, and the merge guardalso verifies that every native issue dependency is closed before changing any
checklist item. #649 must close through its own PR first.