Macro-3 Do-Not-Implement Register — R2-B2 (2026-06-19)

Date: 2026-06-19 · Workstream: R2-B2-MACRO-3-OPTION-D-OWNER-DELEGATE-DECISION-PACKAGE-2026-06-19 (Deliverable 53 of 60) · 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 / decision-prep. The line between this package and implementation. Engineering PASS ≠ authority PASS. Default: HOLD.

1. Purpose

State unambiguously that nothing here is an implementation instruction.

2. Sources / evidence read

Macro-2 do-not-implement register; prompt §4. Main process, no reader-agents.

3. Accepted baseline (carried)

Recommendation + proof-obligation + plan ≠ implementation. Implementation needs a separate write-authorization.

4. Evidence / analysis

Every "proof plan", "readiness map", "branch plan" in this package is a specification of future obligations, not a build instruction. None may be executed as-is.

5. Recommendation / matrix / result — DO NOT

• Do not build the B2 producer from these docs.
• Do not wire any channel from D11/D12.
• Do not create staging from D34.
• Do not write any inspect_* / certify / canonical / ownership row.
• Do not treat any proof plan as "tests to run now".

6. Owner-gated future work

Implementation is gated behind the three decisions + a separate write-authorization.

7. What remains unresolved

Nothing implemented; all design-only.

8. Ready for GPT/Codex review

Yes — Codex should confirm no deliverable reads as an executable build step.