Macro-4 Do-Not-Implement Register — 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 80 of 90) · Editorial revision: rev1 Class: do-not-implement register · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · 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 register of everything that must NOT be implemented from this package. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

Make explicit that none of the 90 design deliverables is an implementation instruction.

2. Sources / evidence read

Non-authorization register (5); prompt §4 (forbidden)/§11 ("It can prepare. It cannot build."); Macro-3 do-not-implement register. Main process, no reader-agents.

3. Accepted baseline (carried)

This macro can prepare, define contracts, design a draft lifecycle, define a bad-input oracle, define gates — it cannot build, write schema, create draft data, run tests, or open TD.

4. Evidence / analysis — do-not-implement list

Designed here (do NOT implement)
the staging workbench (concept only — do not build)
the IO contract envelope (template only — do not bind)
B2 candidate output (do not write candidate/production inspect_*)
delete-fast + no-production-touch (obligations — do not run)
the bad-input oracle (do not execute any test/digest)
the naming/isolation convention (do not create objects)
the entry/staging-build gates (do not open TD / build)

5. Contract / requirement / matrix / result

Reading any deliverable as an implementation step is drift → HOLD. Implementation requires, in order: design-only readiness (this) → GPT → Codex → Owner authority-PASS → rollback plan → runtime-verification plan. None of these later steps is reached.

6. Owner-gated future work

All implementation is Owner-gated; forbidden now.

7. What remains unresolved

Nothing is implemented; everything stays at design.

8. Ready for GPT/Codex review

Yes — Codex should confirm no deliverable is an implementation instruction.