forked from mosaicstack/stack
mos-dt-0andClaude Opus 5
2b85afe4ea
RM-02's per-commit replay needs isolation; the privileged CI step was correctly refused because PR-controlled code executes before Bubblewrap establishes any boundary — the untrusted party would obtain the capability meant to contain it. Ordering defect, not a hardening problem. D-25 is D-19 one layer down: audited party controls the manifest (artifact integrity) became audited party controls the code entering the sandbox (execution integrity). Both reduce to self-verification by the audited party is not verification, and both resolve via an authority outside its control — twice now this mission has derived Builds 1-2 from a security impossibility rather than design preference. Option C ruled independently by the orchestrator and rev-974 before either saw the other. rev-974 added the condition I missed and it matters most: post-merge replay is DETECTION, not PREVENTION, with a defined quarantine/revert response, and must never be presented as equivalent to a pre-merge gate. RM02-REQ-10 revision formally recorded and accepted under RM-02's own clause 4 — original text, restatement, reason — discharging rev-974's review-readiness condition. RM-60 opened for the external pre-execution trust boundary, cross-referenced with RM-59. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>