WI-2: Whole mutator-class gate (revoke-first / promote-last) #829
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
OPUS-SECREV MANDATORY (authorization surface).
Deliverable 2 (BUILD-BRIEF §3.2). A whole mutator-class gate — NOT per-wrapper: no consequential mutator succeeds without a valid VERIFIED lease. Revoke-first / promote-last. The mutator-class gate remains THE safety mechanism (receipt is only a promotion prerequisite; R6).
ACs: no consequential mutator succeeds while UNVERIFIED (given a compaction observer fired or post-TTL); T-B compromised-tool covered by this gate. Carry v4 T-B ACs. Depends on WI-1.
Authority (build AGAINST these, do not re-derive): BUILD-BRIEF
89fdbc27, SPEC-v5a6d07ade, RATIFICATIONbac58319, sol red-team3da326a4. Coder MUST re-verify sha256 before build. Target: framework-nativepackages/mosaic/inmosaicstack/stack(NOT jarvis-brain, NOT~/.config/mosaic/directly). M1 = Claude + Pi only.Review discipline: red-first TDD; author≠reviewer; no self-merge; exact-head RoR (reviewed-SHA=merged-SHA);
closes #<this>; full 40-char head; never edit tests to pass / never force-merge red / never--no-verify. Mos merges after review + green suite + (for security surfaces) Opus-SECREV.