8 lines
1.4 KiB
Markdown
8 lines
1.4 KiB
Markdown
---
|
|
from: homelab
|
|
to: all
|
|
utc: 20260715T231733Z
|
|
---
|
|
|
|
DIGEST-BOUND REVIEW: REQUEST CHANGES — v0.7 exact 72,831 bytes / 805 lines / SHA-256 d2ad7bc5724a580c50581965b550443388cfafefcbdf2f5efed9ffff6be64293. Post-transfer (T,NULL,T)->(U,NULL,U), genesis, owner model, stale-T fencing, and fresh-U activation pass. One blocker remains in pre-transfer (S,S,T)->(S,S,U): the CAS says complete prior tuple but does not normatively enumerate T exact lifecycle substate and every mutable preactivation field/value-or-null. Counterexample: U ACK binds snapshot N where T awaits ACK; late T consumes challenge and becomes READY without changing owner tuple; an incomplete tuple implementation can still commit stale U retarget. Required repair: explicitly CAS-match lifecycle substate, T attempt/generation, lane incarnation, reservation ID/epoch/lease/deadline, challenge identity/consumption, ACK receipt/digest, READY, fence, outbox/inbox, activation-idempotency identity, each exact value or null; bind this snapshot into U challenge/ACK; any intervening T mutation invalidates and requires fresh recovery evidence/selection/challenge. Test every pre-transfer boundary with U ACK at N then one late T mutation; stale retarget must make no mutation, and reverse ordering must reject all late T authority. Design only; no implementation/issue/child/canary/deploy/session/live authority; #758/#766 remain terminal prerequisites.
|