Macro-4 Disposable Draft Surface Requirements — R2-B2 (2026-06-19)
Macro-4 Disposable Draft Surface 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 42 of 90) · Editorial revision: rev1
Class: disposable draft surface 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 properties a disposable draft surface must have to be safe to "draft freely / delete fast." Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Pin the surface-level properties that make "nháp thoải mái" safe.
2. Sources / evidence read
Pilot-slice staging IO contract §3/§9; workbench concept (6); FRESH existing IU staging tables (to distinguish). Main process, no reader-agents.
3. Accepted baseline (carried)
The freedom to iterate comes from disposability + isolation, not relaxed rules — the fail-closed Điều 0-G rules still apply inside the workbench.
4. Evidence / analysis — surface requirements (DDS)
| # | Requirement |
|---|---|
| DDS-1 | Isolated: a distinct disposable namespace, never birth_registry/iu_core.*/unit_edit_draft (FRESH production objects) |
| DDS-2 | Disposable: removable as one unit with no production cascade |
| DDS-3 | Rule-faithful: mirrors the B3 inspect_* shape + Điều 0-G fail-closed rules (no relaxed rules) |
| DDS-4 | Candidate-only: produces candidate inspect_*, never production |
| DDS-5 | Evidence-bearing: emits staging-tagged, records-not-decides evidence |
| DDS-6 | Proof-friendly: supports a before/after production snapshot |
5. Contract / requirement / matrix / result
A surface meeting DDS-1…DDS-6 is safe to draft on and throw away. FRESH note: the existing iu_core staging tables are production IU-pipeline surfaces and do not satisfy DDS-1 as a B2 workbench — the B2 surface must be separate and new. No surface is built here.
6. Owner-gated future work
Building a DDS-compliant surface is Owner-gated future TD; forbidden now.
7. What remains unresolved
The surface materialization (separate schema/db) is FUTURE_TECHNICAL_DESIGN_REQUIRED.
8. Ready for GPT/Codex review
Yes — Codex should confirm the surface is isolated from all FRESH production objects.