Macro-4 Staging Workbench Boundary — 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 7 of 90) · Editorial revision: rev1 Class: staging workbench boundary · 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.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. Defines exactly what is inside the workbench and what it must never cross. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Draw the hard line between the disposable workbench and everything production.

2. Sources / evidence read

Pilot-slice staging IO contract §6 (forbidden outputs)/§7 (separation)/§12 (compat); inspect-producer §5/§13; FRESH iu_create.gateway.* + canonical-write evidence. Main process, no reader-agents.

3. Accepted baseline (carried)

The load-bearing separation: candidate inspect results live on the staging surface, never on production birth_registry; B4 (fn_birth_auto_certify) reads only production inspect_* and must never see staging candidates.

4. Evidence / analysis — boundary

Inside the workbench	Outside (never crossed)
disposable input projection (copy of uncertified-row shape)	production birth_registry rows
candidate inspect_* columns/markers	production inspect_pen/stamp/gate
staging-tagged S7-shaped evidence	production S7 / approval path (S1, Điều 32)
one staging run = one rollback unit	B4 auto-certify trigger; certified/certified_at
Điều 0-G fail-closed rules (mirrored)	canonical_address/owner/jsonb_profile/status; KG universal_edges; iu_create canonical gateway

5. Contract / requirement / matrix / result

The boundary is one-directional: production is never read from staging as authority; staging candidates are never read into production. The only legitimate bridge is an explicit Owner-gated promotion (firewall, Deliverable 48). Consumer isolation (B4 never sees staging) makes a staging experiment incapable of triggering a production certify — by construction.

6. Owner-gated future work

Materializing this boundary (separate schema/namespace, tagging) is Owner-gated future TD; forbidden now.

7. What remains unresolved

The exact isolation mechanism (separate schema vs separate DB vs tagged disposable surface) is FUTURE_TECHNICAL_DESIGN_REQUIRED.

8. Ready for GPT/Codex review

Yes — Codex should attack any path by which a candidate could reach a production field (the load-bearing isolation failure, BAD-14).