Macro-2 → Macro-3 Preconditions and Safety Locks — R2-B2 (2026-06-19)
Macro-2 → Macro-3 Preconditions and Safety Locks — R2-B2
Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 37 of 45) · Editorial revision: rev1
Class: Macro-3 preconditions + safety locks · READ-ONLY · NON-ENACTING · NON-AUTHORIZING · NO macro authorized · NO write performed.
Metadata convention. Editorial revision (rev1) only. AgentData storage revision/
content_lengthauthoritative at read time; not pinned here.
Precondition lock. States the preconditions Macro-3 must satisfy and the safety locks it must carry. It authorizes no macro.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. Macro-3 preconditions + carried safety locks. It authorizes nothing.
Engineering PASS ≠ authority PASS. Default disposition: HOLD. No macro authorized; no decision; no DB write/DDL/DML; no TD; no blocker resolved; v0.1 not overwritten; v0.2 not authority.
Evidence basis — design synthesis of Deliverables 1–36. Reading discipline: main process, no reader-agents.
1. Purpose
Pin what must be true before Macro-3 opens, and the locks it must carry, so the next macro cannot drift.
2. Sources / evidence read
Deliverable 36 (Macro-3 scale plan); the macro safety locks (prompt §6 S/H/F); the do-not-implement register (Deliverable 39). Read directly, main process.
3. Accepted baseline (carried)
Macro-3 is branched by the Owner's Macro-2 decision; default = another read-only/decision-prep macro at 45–50 deliverables; no automatic TD/build.
4. Macro-3 preconditions (all Owner-gated)
| # | Precondition | Status today |
|---|---|---|
| PC-1 | GPT reviews the 45 Macro-2 files; if accepted, Codex reviews | pending |
| PC-2 | Owner picks the Macro-2 path (Q1: default D) | pending (HOLD) |
| PC-3 | If D: Owner takes (or schedules) the three decisions (channel/Đ0-G/S2) — or explicitly keeps read-only | pending |
| PC-4 | Macro-3 scope chosen per the branch table (Deliverable 36) | pending |
| PC-5 | No precondition implies a write — all remain Owner-gated | held |
5. Safety locks Macro-3 must carry (verbatim discipline)
| Lock | Requirement |
|---|---|
| Primary block | B2 the only primary block; B5/B7 dependency-only; R1/KG cross-check-only |
| Channel | RECOMMENDATION_ONLY — NOT AUTHORITY unless Owner decided outside the macro; CHANNEL_AUTHORITY_DRIFT → HOLD |
| Owner | no S2 assignment; OWNER_ASSIGNMENT_DRIFT → HOLD |
| Source | no Đ0-G adoption; SOURCE_ADOPTION_DRIFT → HOLD |
| TD | no actual TD; ACTUAL_TD_DRIFT → HOLD |
| Staging | no staging schema/corpus; STAGING_SCHEMA_OR_CORPUS_DRIFT → HOLD |
| Tool lock | v0.1-stable/FIX7 V3 not overwritten; v0.2-hardening not authority |
| LEGO | every deliverable a separate control surface; else NOT_LEGO_COMPATIBLE → HOLD |
| Default | engineering PASS ≠ authority PASS; Default HOLD |
6. Owner-gated future work
Opening Macro-3 (after PC-1…PC-5) is the Owner's act; forbidden now.
7. What remains unresolved
- All preconditions pending; no macro authorized.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as the Macro-3 preconditions + safety locks.
Core rule: Macro-3 opens only after GPT→Codex→Owner; it must carry every lock; no macro authorized.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.