Macro-4 Draft Object Birth Contract — R2-B2 (2026-06-19)
Macro-4 Draft Object Birth Contract — 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 14 of 90) · Editorial revision: rev1
Class: draft object birth contract · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CONCEPT-ONLY · NO write performed.
Metadata convention. Editorial revision (rev1) only. Storage revision/
content_lengthauthoritative at read time.
Disambiguation. "Birth" = a draft artifact coming into existence in the workbench. Not
birth_registry/B1/B4. No production birth/certify touched.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The contract for creating a draft object cleanly and disposably. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Define how a draft object is born so it is self-identifying, scoped to a run, and deletable.
2. Sources / evidence read
Draft lifecycle (13); workbench naming convention (9); pilot-slice staging IO contract §4 (input)/§5 (output). Main process, no reader-agents.
3. Accepted baseline (carried)
Everything entering the workbench is a copy/sample; everything produced is a candidate on a disposable surface.
4. Evidence / analysis — birth contract
| Field | Value |
|---|---|
| Input | a disposable projection of uncertified-row shape (not live rows) |
| Identity | a unique staging run id + "candidate" designation |
| Surface | the disposable workbench namespace only (never production/iu_core) |
| Genuine | candidate inspect_* set only on a real per-stage pass (no blanket now()) |
| Fail mode | malformed draft input → reject (no fabricated pass), append to staging evidence |
5. Contract / requirement / matrix / result
A born draft object is fully enumerable by its run id (precondition for delete-fast) and carries no production reference. Birth never sets production inspect_*/certified/canonical fields.
6. Owner-gated future work
Creating a draft object against a built surface is Owner-gated; forbidden now.
7. What remains unresolved
The materialization of "born" is FUTURE_TECHNICAL_DESIGN_REQUIRED.
8. Ready for GPT/Codex review
Yes — Codex should confirm a born draft is run-scoped and production-free.