Phase 2: generate legal deleted-bridge paired tapes (#104) #657
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!657
Loading…
Reference in a new issue
No description provided.
Delete branch "phase2/p2-11-b-deleted-bridge"
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 #104 (P2-11-B).
Summary
Generate the protocol's deleted-bridge pairs as complete sealed tapes before
execution. Arm B delegates each target leaf through a unique temporary capability,
then legally deletes that capability and its holder. The executed cuts have the
same live authority and access as A, with complete historical evidence retained.
Scope
Prospective actor roles, exact assignment/rights draws, sizes 8/32/128 and the
common 128-epoch continuation. Tests cover all seven frozen mechanisms, 84 smoke
cells, 14 zero/all-target boundary cells, invalid sizes and an independent Python
reference for complete tapes and role mappings. A_clone and saved minimum witnesses
remain #105.
Design intent
Every bridge creation and teardown is an actual legal event. Resolve logical
handles through the executor's physical bindings; the arms need not share numeric
edge IDs or cut times. Preserve root origins, immutable ancestry and deletion
records. The independent Read policy excludes extinct bridges from denominators.
The generator has no runtime-state or outcome input and never resamples a seed.
Phase discipline
Protocol 2.2 / backlog 2.2.1; prerequisites #100 and #101 are closed. Fixtures use
development seeds and establish correctness. No campaign, statistical conclusion
or recovery result is supplied by this leaf. Complete csaI still includes the
requested Phase 5 supplement.
Verification
165e4e734e4f7eda1463bb5d9eeb7391e29afdc5passed all 192 tests without skipsin GCC Debug (400.31 s), GCC Release (42.76 s) and Clang Debug ASan/UBSan with
-g -O1and one test worker (603.73 s).including legal prefixes, exact projections/access, full event/source bindings,
policy targets, origins/depths/deletions and immutable cuts.
2,784 variates; both earlier replay reference fingerprints remain unchanged.
ffc0e7f6a9f525566596b18ced333df52198116f8da6987f4e383e4cbefb1692. Records are underartifacts/backlog/2.2.1/P2-11-B/.are required before the one-step issue checklist update and merge.
Integration validation
Accepted lineage-swap main
aef917b9396e4368ad86e4946a9b9aa6a29f39b4is merged at sourceeb2c796b2f676fa08bb2de3405fc3d204cd22fe7.All original deleted-bridge implementation bytes are unchanged. The two CMake
files retain both complete families: the exact union of the original192-test
inventories, with92 common tests, is292 tests. Every integrated Release test
passes without skips. Both accepted CI fixes #653 and #655 are included.
Integration evidence has SHA-256
ee9c899ce775dd4bd92439dcb568a2afd5daf5469667d344efec9d063e0c848b.Original source-bound receipts remain intact;
integration.jsonidentifiesthe two superseded build-file hashes. All eight final-head remote checks remain
mandatory before checking #104 once and merging this PR.
Smoke profile correction after the failed remote integration
The previous head
3b13d6ccb61d9277374dbd5b707e64e69674cb14hit both90-minute smoke deadlines after 190/189 passing tests. Both sanitizer suites
passed; neither incomplete smoke attempt is accepted. Separate bug #661 adds
explicit
-g -O1to the GCC Debug smoke configuration. No test, scientific source,compiler/container, sanitizer setting, worker count or timeout is changed.
Source
d01ec511de58981c91f18b1b0425e4fa8687f76bintegrates that fix andpasses the complete unchanged 292-test inventory locally with one worker
(225.02 seconds), no failures and no skips. All 124 C++ translation units retain
-g, select-O1and omitNDEBUG. All hooks and the frozen PDF scope pass.The original source-bound receipts remain unchanged; the new
integration-bug-661.jsonrecords the corrected profile and failed attempts.Failure and corrected-profile evidence, SHA-256
77f25e389dea0edaf4291b1d635c2f03dcd56be252eb831fe4fc73e526ad5257.Native prerequisite #661 is now attached. Require all eight final-head contexts
on both the fix and this consumer before merging the fix. Then require the
closed prerequisites and this PR's own complete checks before checking #104
once and merging. Later stacked PRs must reconcile this new predecessor head.