Macro-5 B2 Candidate Delete Contract Refinement — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 37 of 110) · Editorial revision: rev1 Class: B2 delete contract refinement · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · B2-ONLY · NO write performed.

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

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. Refines the Macro-4 B2 rollback/delete contract; one-unit + downstream-certify preserved. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Carry the one-run delete unit forward, keeping the downstream-certify subtlety visible.

2. Sources / evidence read

Macro-4 B2 rollback/delete contract (D33); delete candidate (28); rollback model (20). Main process, no reader-agents.

3. Accepted baseline (carried)

One producer run = one rollback/delete unit; in the workbench deletion is the rollback; HOLD-2 OPEN.

4. Evidence / analysis — refinement (build-context only)

Clarification	For the workbench build
unit	one run = one delete unit (run-id/namespace enumerable)
workbench	candidate inspect_* + staging evidence delete together; production untouched
downstream-certify	production unwind of a triggered B4 certify is Owner-gated future TD
no script	no DELETE/UPDATE/migration written

5. Candidate / requirement / gate / result

If a clean per-run unit (incl. downstream-certify) cannot be defined, the design is not write-authorized — fail-closed. HOLD-2 remains OPEN. No delete is executed here.

6. Owner-gated future work

Defining/executing the delete mechanism is Owner-gated; forbidden now.

7. What remains unresolved

HOLD-2 OPEN; downstream-certify unwind undecided.

8. Ready for GPT/Codex review

Yes — Codex should confirm the unit is one run and writes no script.