Macro-4 Staging Workbench Build-Not-Authorized Lock — 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 12 of 90) · Editorial revision: rev1 Class: build-not-authorized lock · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · STAGING_BUILD_REQUIRED_BUT_FORBIDDEN guard · 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. The lock that holds the workbench at concept and forbids building it. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Prevent any of the workbench concept files (6–11) from being read as authorization to build staging.

2. Sources / evidence read

Pilot-slice staging IO contract §14 (Owner-gated future work); prompt §3 staging lock; TD-readiness §11. Main process, no reader-agents.

3. Accepted baseline (carried)

"This macro may design readiness for a staging workbench. It must not create it." Forbidden: CREATE TABLE / ALTER TABLE / INSERT / UPDATE / DELETE / migration / schema file / corpus / staging table / draft corpus / production data copy.

4. Evidence / analysis

The workbench concept (Deliverables 6–11) defines properties, boundaries, lifecycle, naming, delete-fast, and no-production-touch. None of these is a build artifact: no schema, no DDL, no table/column, no SQL, no corpus, no extraction. The staging surface does not exist after this macro.

5. Contract / requirement / matrix / result — drift trigger (→ HOLD)

Drift	Token	Disposition
A staging schema/table/corpus is created	STAGING_BUILD_REQUIRED_BUT_FORBIDDEN / STAGING_TD_DRIFT	HOLD
A production sample is extracted into a draft	(same)	HOLD
Status this run: NOT triggered. The staging build is authorized only after the staging-build authorization gate (Deliverable 57) is Go and the Owner approves — neither holds.

6. Owner-gated future work

Building the workbench is Owner-gated future TD; forbidden now.

7. What remains unresolved

The build remains forbidden; the build-authorization gate is NO-GO (Deliverable 58).

8. Ready for GPT/Codex review

Yes — Codex should confirm no workbench deliverable contains a build artifact.