Macro-4 Draft Object Lifecycle — 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 13 of 90) · Editorial revision: rev1 Class: draft object lifecycle · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CONCEPT-ONLY · NO write performed.

Metadata convention. Editorial revision (rev1) only. Storage revision/content_length authoritative at read time.

Disambiguation. "Draft object birth/lifecycle" here = the LEGO lifecycle of a disposable draft artifact (a candidate B2 design, a draft producer, a draft surface). It is not the birth_registry birth of an entity. No production birth/certify is touched.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. Defines the born/checked/replaced/deleted lifecycle of any draft object in the workbench. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Answer macro question 3 — what draft object lifecycle is required? — so each draft part is independently born/checked/replaced/rolled-back.

2. Sources / evidence read

Owner LEGO invariant ("born-tested-replaced-rolled-back separately"); pilot-slice staging IO contract §9/§10; inspect-producer §10 (one producer run = one unit). Main process, no reader-agents.

3. Accepted baseline (carried)

Each LEGO part can be drafted, tested, deleted, and replaced independently; parts connect only through standardized IO contracts; failed drafts must not touch production.

4. Evidence / analysis — lifecycle

Phase	Contract (Deliverable)	Property
Born	draft-object birth contract (14)	a draft is created on the disposable surface, tagged with a run id
Checked	draft-object check contract (15)	a draft is exercised/verified in isolation; fail-closed
Replaced	draft-object replace contract (16)	a wrong draft is swapped for another with no cascade
Deleted	draft-object delete contract (17)	a draft is removed in one delete-fast unit
(Never) Promoted	promotion-forbidden register (18)	no automatic draft→production promotion

5. Contract / requirement / matrix / result

The lifecycle is closed inside the workbench: every phase operates on disposable artifacts, leaves production untouched, and connects to other LEGO parts only via the IO contract envelope (Deliverable 19). Promotion is excluded from the lifecycle — it is a separate Owner gate.

6. Owner-gated future work

Implementing any lifecycle phase against a built surface is Owner-gated; forbidden now.

7. What remains unresolved

The lifecycle is conceptual; no draft object is created here.

8. Ready for GPT/Codex review

Yes — Codex should confirm every phase is independently reviewable and that promotion is excluded.