Macro-4 Staging Workbench Delete-Fast Requirements — R2-B2 (2026-06-19)
Macro-4 Staging Workbench Delete-Fast Requirements — R2-B2 (2026-06-19)
Date: 2026-06-19 · Workstream: R2-B2-MACRO-4-STAGING-WORKBENCH-IO-CONTRACT-TD-ENTRY-GATE-2026-06-19 (Deliverable 10 of 90) · Editorial revision: rev1
Class: delete-fast requirements (workbench) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.
Metadata convention. Editorial revision (rev1) only. Storage revision/
content_lengthauthoritative at read time.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The delete-fast requirements the workbench surface must satisfy. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Make "deleted quickly" a hard requirement on the workbench, not an aspiration.
2. Sources / evidence read
Pilot-slice staging IO contract §9 (delete-fast boundary); bad-input/delete-fast plan §8 (delete-fast evidence); Macro-3 delete-fast risk map. Main process, no reader-agents.
3. Accepted baseline (carried)
The delete-fast boundary = the entire workbench surface as one disposal unit (input projection + candidate outputs + staging evidence), deletable in one move.
4. Evidence / analysis — requirements (DFW)
| # | Requirement |
|---|---|
| DFW-1 | One disposal unit: input + candidate inspect_* + staging evidence delete together |
| DFW-2 | Fast: rejecting a design = "delete the surface" — no surgical unwind, no per-row repair |
| DFW-3 | Total: all candidates (including bad-input candidates) and all staging evidence removed; nothing survives outside the unit |
| DFW-4 | Isolated: the unit contains no production rows, so disposal cannot cascade into B1/B3/B4 or any shared surface |
| DFW-5 | Verifiable: after disposal, production birth_registry (incl. inspect_*, certified, canonical_address) is byte/count-identical and the surface is empty/absent |
| DFW-6 | No leftover references: no canonical address, no certified row, no KG edge attributable to the disposed run |
5. Contract / requirement / matrix / result
If delete-fast cannot remove a candidate (BAD-15 / F-OPEN-9), the staging design is defective and rejected. The delete-fast mechanism (DELETE/DROP sequence) is FUTURE_TECHNICAL_DESIGN_REQUIRED — no SQL written here.
6. Owner-gated future work
Defining/executing the delete-fast mechanism is part of the staging build — Owner-gated; forbidden now.
7. What remains unresolved
The mechanism and its proof harness are future TD; here only the requirements exist.
8. Ready for GPT/Codex review
Yes — Codex should confirm the unit is total and isolated (no production residue possible).