Macro-5 Delete-Fast Verification Delete-Unit — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 61 of 110) · Editorial revision: rev1 Class: delete-fast verification delete-unit · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · 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. The delete-unit definition a verification must enforce (DF-1/DF-2). Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Define the one enumerable unit that a single delete operation removes.

2. Sources / evidence read

Macro-4 delete-fast unit-of-deletion (D38); delete candidate (28); naming model (16). Main process, no reader-agents.

3. Accepted baseline (carried)

One run = one delete unit; the unit holds no production rows; enumerable by a single identifier.

4. Evidence / analysis — delete-unit

Granularity	Unit contents	Identified by
per-run	input projection + candidate inspect_* + staging evidence	staging run id
per-surface	all runs' artifacts on the disposable workbench	workbench namespace
never includes	any production birth_registry row, KG edge, or canonical field	—

5. Candidate / requirement / gate / result

The unit must be enumerable by a single identifier (run id/namespace) so one operation removes all of it (DF-1) with no production member (DF-2). No unit is created or deleted here. A unit that cannot enumerate its artifacts is defective (BAD-15).

6. Owner-gated future work

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

7. What remains unresolved

The disposal mechanism is FUTURE_TECHNICAL_DESIGN_REQUIRED.

8. Ready for GPT/Codex review

Yes — Codex should confirm the unit is one enumerable set with no production member.