Macro-4 Draft Object Delete Contract — 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 17 of 90) · Editorial revision: rev1 Class: draft object delete contract · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CONCEPT-ONLY · NO write performed.

Metadata convention. Editorial revision (rev1) only. Storage revision/content_length authoritative at read time.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. How a draft object is deleted cleanly and totally. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define the "deleted separately" property: one draft = one disposal unit, removable with no residue.

2. Sources / evidence read

Workbench delete-fast requirements (10); bad-input/delete-fast plan §8; pilot-slice staging IO contract §9. Main process, no reader-agents.

3. Accepted baseline (carried)

Delete-fast removes all candidate outputs (including bad-input candidates) and all staging evidence; nothing survives outside the unit.

4. Evidence / analysis — delete contract

Property	Requirement
Unit	one draft object's input + candidate inspect_* + evidence = one deletable unit
Total	no candidate or evidence of the run survives delete
Isolated	no production row touched; no cascade
Verifiable	before/after proof: surface empty, production identical
Fail-closed	if a candidate cannot be removed, the design is rejected (BAD-15)

5. Contract / requirement / matrix / result

The delete contract = DFW-1…DFW-6 (Deliverable 10) applied at the per-draft granularity. The delete mechanism is FUTURE_TECHNICAL_DESIGN_REQUIRED; no DELETE/DROP written here.

6. Owner-gated future work

Executing a delete against a built surface is Owner-gated; forbidden now.

7. What remains unresolved

The delete mechanism and its proof are future TD.

8. Ready for GPT/Codex review

Yes — Codex should confirm delete is total, isolated, and verifiable.