KB-1080

Macro-4 Delete-Fast Unit of Deletion — R2-B2 (2026-06-19)

3 min read Revision 1
laws-newR2-B2macro-4delete-fastunit-of-deletionnon-authorizing2026-06-19

Macro-4 Delete-Fast Unit of Deletion — 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 38 of 90) · Editorial revision: rev1 Class: delete-fast unit of deletion · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · 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. Defines the single unit a delete-fast operates on. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Make precise what "one unit" means so disposal is total and bounded.

2. Sources / evidence read

Pilot-slice staging IO contract §9 (one disposal unit)/§10 (one staging run = one rollback unit); inspect-producer §10. Main process, no reader-agents.

3. Accepted baseline (carried)

The delete-fast boundary = the entire staging surface as one disposal unit (input projection + candidate inspect_* + staging evidence); a single staging run = one rollback unit.

4. Evidence / analysis — the unit

Granularity Unit contents Identified by
Per-run input projection + candidate inspect_* + staging evidence of that run 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. Contract / requirement / matrix / result

The unit must be enumerable by a single identifier (run id / namespace) so one operation removes all of it. A unit that cannot enumerate all its artifacts is defective (residue risk, BAD-15). No unit is created or deleted here.

6. Owner-gated future work

Materializing the unit (namespace/run-id scheme) is Owner-gated future TD; forbidden now.

7. What remains unresolved

The concrete identifier scheme is FUTURE_TECHNICAL_DESIGN_REQUIRED (see naming convention, Deliverable 9).

8. Ready for GPT/Codex review

Yes — Codex should confirm the unit is enumerable and excludes all production state.

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro4-delete-fast-unit-of-deletion-2026-06-19.md