Macro-5 Staging TD Candidate Naming Model — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 16 of 110) · Editorial revision: rev1 Class: non-executable staging TD candidate (naming model) · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.

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

NON_EXECUTABLE_TD_CANDIDATE. Convention, not schema. No DDL/table/column; no object created.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. A naming discipline so draft objects are unmistakable and disposable-by-name. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Refine Macro-4's naming convention into a candidate model the delete-fast unit can rely on.

2. Sources / evidence read

Macro-4 staging workbench naming convention (D9); FRESH 2026-06-19 existing names (iu_core.iu_staging_*, unit_edit_draft); operating-rules ("no hardcode"). Main process, no reader-agents.

3. Accepted baseline (carried)

Candidate results carry a STAGING marker + staging run id; the exact strings are FUTURE_TECHNICAL_DESIGN_REQUIRED.

4. Evidence / analysis — naming model (properties, not strings)

Element	Property	Why
surface prefix	a distinct disposable namespace, never birth_registry / iu_core.* / public.unit_edit_draft	collision-free vs FRESH production names
run id	every draft run carries a unique staging run id	scopes the delete-fast unit
candidate tag	candidate inspect_* marked "candidate"	never confusable with production inspect_*
evidence tag	staging evidence tagged STAGING	never read into a production decision
derivation	names derived from a run id, not hardcoded	one query enumerates a run for disposal

5. Candidate / requirement / gate / result

The model fixes properties (collision-free, run-id-scoped, enumerable, non-hardcoded), not strings. FRESH check confirms no production object would collide. No name is created.

6. Owner-gated future work

Choosing and applying the concrete scheme is part of the build — Owner-gated; forbidden now.

7. What remains unresolved

The concrete prefix/schema choice (SB-4) is undecided.

8. Ready for GPT/Codex review

Yes — Codex should confirm no proposed name collides with a FRESH production object and no DDL is written.