Macro-5 Staging Object: Delete Candidate — R2-B2 (2026-06-19)
Macro-5 Staging Object: Delete Candidate — R2-B2 (2026-06-19)
Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 28 of 110) · Editorial revision: rev1
Class: staging object candidate (delete) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time.
NON_EXECUTABLE_TD_CANDIDATE. Conceptual object only. No DELETE/DROP/script; do not delete anything.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The delete conceptual object: the one disposal unit. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Describe the disposal unit so a run can be thrown away cleanly, production untouched.
2. Sources / evidence read
Macro-4 delete-fast unit-of-deletion (D38); rollback model (20); delete-fast master requirements (D37, DF-1…DF-7). Main process, no reader-agents.
3. Accepted baseline (carried)
One run = one delete unit; the unit holds no production rows; deletion is the rollback.
4. Evidence / analysis — delete candidate
| Aspect | Description (no schema) |
|---|---|
| role | the enumerable set of all artifacts of one run |
| field family | run-id / namespace (enumerator) |
| contents | input projection + candidate inspect_* + staging evidence of that run |
| never includes | any production birth_registry row, KG edge, or canonical field |
| guarantee | one operation removes all of it (DF-1); no leftover (DF-5) |
5. Candidate / requirement / gate / result
The delete object must be enumerable by a single identifier so one operation removes the whole unit. A unit that cannot enumerate its artifacts is defective (residue risk, BAD-15). No unit is created or deleted here.
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 delete object is one enumerable unit with no production member.