Macro-4 Staging vs Actual-TD Separation — R2-B2 (2026-06-19)
Macro-4 Staging vs Actual-TD Separation — 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 59 of 90) · Editorial revision: rev1
Class: staging vs actual-TD separation · 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. Distinguishes the two gates — staging build vs actual B2 TD — so they are never conflated. Engineering PASS ≠ authority PASS. Default: HOLD.
1. Purpose
Keep the staging-build gate (57) and the actual-TD gate (55) as separate Owner decisions with different prerequisites.
2. Sources / evidence read
Entry gate v2 (55); staging build authorization gate (57); TD-readiness §11/§14. Main process, no reader-agents.
3. Accepted baseline (carried)
A disposable staging surface is a precondition (G-6/F-6/PO-9) for actual B2 TD; building staging is itself a smaller, separately-gated act.
4. Evidence / analysis — separation
| Dimension | Staging build | Actual B2 TD |
|---|---|---|
| What it produces | a disposable workbench surface | the producer technical design |
| Gate | SB-1…SB-6 (Deliverable 57) | G-1…G-11 (Deliverable 55) |
| Depends on | workbench concept accepted + Owner build-authorization | staging surface exists (G-6) + channel/S2/Điều 0-G decided |
| Touches production? | no (disposable, isolated) | no at design time; producer build is later still |
| Status today | NO-GO | NO-GO |
5. Contract / requirement / matrix / result
The two are ordered and distinct: staging build (if authorized) comes before actual TD can satisfy G-6, but neither is authorized now. Conflating them (treating a workbench design as TD authorization, or vice versa) is drift → HOLD. Status this run: NOT triggered.
6. Owner-gated future work
Both gates are Owner-gated and separate; forbidden now.
7. What remains unresolved
Both gates NO-GO; the Owner decides each independently (Deliverable 60 maps the branches).
8. Ready for GPT/Codex review
Yes — Codex should confirm the two gates are not conflated and both are NO-GO.