Macro-4 Delete-Fast Evidence Requirements — R2-B2 (2026-06-19)
Macro-4 Delete-Fast Evidence Requirements — 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 39 of 90) · Editorial revision: rev1
Class: delete-fast evidence requirements · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.
Metadata convention. Editorial revision (rev1) only. Storage revision/
content_lengthauthoritative at read time.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The before/after evidence a delete-fast must yield. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Make delete-fast provable: define the evidence required, not a result.
2. Sources / evidence read
Bad-input/delete-fast plan §8 (delete-fast evidence)/§9 (rollback boundary); operating-rules AP-CLOSE. Main process, no reader-agents.
3. Accepted baseline (carried)
Delete-fast must be provable via a before/after comparison around disposal; "PASS/FAIL không có số liệu" is an anti-pattern.
4. Evidence / analysis — required evidence (DFE)
| # | Evidence |
|---|---|
| DFE-1 | Pre-disposal inventory: candidate-row count, candidate inspect_* count, staging-evidence count + a run checksum/id |
| DFE-2 | Post-disposal proof: surface empty/absent — zero candidate rows, zero candidate inspect_*, zero residual evidence for the run |
| DFE-3 | Totality: all candidates (incl. bad-input candidates) removed; none survive |
| DFE-4 | Rollback evidence: the disposed unit = exactly one run (run id), not partial/cross-run |
| DFE-5 | No-downstream proof: certified/certified_at unchanged for all production rows during the run |
5. Contract / requirement / matrix / result
The evidence is the shape a future delete-fast must emit; no snapshot/comparison is run here. A delete-fast that cannot produce DFE-1…DFE-5 is rejected.
6. Owner-gated future work
Building the evidence harness is Owner-gated; forbidden now.
7. What remains unresolved
The concrete snapshot queries are FUTURE_TECHNICAL_DESIGN_REQUIRED.
8. Ready for GPT/Codex review
Yes — Codex should confirm the evidence is before/after and proves totality + no-downstream.