Macro-4 Staging Workbench Concept — 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 6 of 90) · Editorial revision: rev1 Class: staging workbench concept · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · CONCEPT-ONLY · STAGING_BUILD_REQUIRED_BUT_FORBIDDEN guard · NO schema/table/corpus · NO write performed.

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

Concept-only lock. This defines what the B2 staging workbench should be, conceptually. It writes no schema, table, column, SQL, DDL, corpus, or extraction plan. Any drift toward a built surface is STAGING_BUILD_REQUIRED_BUT_FORBIDDEN → HOLD.

---

0. Status and non-authorization

STATUS: PASS — engineering / design-only. A complete conceptual definition of the disposable B2 workbench. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Answer macro question 1 — what should the B2 staging workbench look like conceptually?

2. Sources / evidence read

Pilot-slice-0 staging IO contract §3 (objective)/§7 (separation)/§9 (delete-fast); inspect-producer §5 (B2 boundary); TD-readiness §11 (staging dependency); FRESH information_schema scan of existing staging-like tables. Main process, no reader-agents.

3. Accepted baseline (carried)

Staging is a disposable workshop, not a second production path: everything entering is a copy/sample; everything produced is a candidate on a disposable surface; nothing it does writes production birth_registry, certifies, canonicalizes, mints identity, or touches the KG (pilot-slice §3/§6).

4. Evidence / analysis

The workbench is the surface where a candidate B2 producer can be exercised end-to-end against a copy with zero production effect — operationalizing "tested alone / deleted-rebuilt alone." FRESH boundary note: the production substrate already contains IU-pipeline staging objects (iu_core.iu_staging_payload≈4 rows, iu_core.iu_staging_record≈3 rows, their v_* views, public.unit_edit_draft). These are production surfaces of the IU (incremental-update) lineage governed by the enforced iu_create gateway (block_after_guard, marker app.canonical_writer=fn_iu_create). The B2 workbench is separate and new; it must not reuse, alias, or write these IU objects as if they were scratch.

5. Contract / requirement / matrix / result

Property	Required value
Nature	draft-only, disposable, isolated
Mirrors	the B3 inspect_* shape + Điều 0-G fail-closed rules
Produces	candidate inspect_pen/stamp/gate on the disposable surface only
Never	production write / certify / canonical / identity mint / KG / owner-row / source-adopt
Disposal	one delete-fast unit; production provably untouched
Promotion	only via an explicit Owner gate (firewall) — never automatic

6. Owner-gated future work

Building the workbench (schema/tables/isolation) is Owner-gated future TD; forbidden now.

7. What remains unresolved

The workbench is defined, not built; how a disposable surface is materialized is FUTURE_TECHNICAL_DESIGN_REQUIRED.

8. Ready for GPT/Codex review

Yes — Codex should confirm the concept stays disposable/isolated and never collapses into the production IU staging tables.