KB-1C06

Macro-5 Staging Build Authorization Question — R2-B2 (2026-06-19)

3 min read Revision 1
laws-newR2-B2macro-5staging-buildauthorization-questionnon-authorizing2026-06-19

Macro-5 Staging Build Authorization Question — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-5-STAGING-BUILD-AUTHORIZATION-PACKAGE-2026-06-19 (Deliverable 7 of 110) · Editorial revision: rev1 Class: staging build authorization question · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO write performed.

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


0. Status and non-authorization

STATUS: PASS — engineering / design-only. States the exact authorization the Owner must approve before any build. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Answer macro question 2 — what exact staging build authorization must the Owner approve later? — as one precise sentence.

2. Sources / evidence read

Staging build authorization ballot (6); Macro-4 staging build gate (D57); prompt §9.3. Main process, no reader-agents.

3. Accepted baseline (carried)

Authorization must be explicit, scoped, and separate from actual-TD authorization (the two gates are distinct and ordered).

4. Evidence / analysis — the precise question

"Do you, the Owner, authorize building one disposable, isolated B2 staging workbench — separate from production birth_registry, iu_core.*, unit_edit_draft, and the iu_create gateway — that produces only candidate inspect_*, is deletable as one unit, provably never touches production, and may never auto-promote — under a named isolation scheme, with a delete-fast + no-production-touch verification harness, and with no actual B2 TD opened?"

Element of the ask Must be true
disposable + isolated separate namespace; collision-free vs FRESH production names
candidate-only candidate inspect_*; no production write
one delete unit DF-1…DF-7 satisfiable
no production touch before/after proof obligations accepted
no auto-promotion promotion firewall stands

5. Candidate / requirement / gate / result

The question is stated, not asked; the answer is the Owner's. Until answered, staging build = NO-GO. A "yes" authorizes only a build, never a certify/canonical/TD.

6. Owner-gated future work

Posing and answering this question are Owner acts; forbidden now.

7. What remains unresolved

Unanswered; the isolation scheme (SB-4) is undecided.

8. Ready for GPT/Codex review

Yes — Codex should confirm the question scopes a build only, not a certify/TD.

Back to Knowledge Hub knowledge/dev/laws-new/newlaws/consolidation/macro5-staging-build-authorization-question-2026-06-19.md