Macro-2 Next Macro-3 Scope Plan (45 Deliverables) — R2-B2 (2026-06-19)
Macro-2 Next Macro-3 Scope Plan (45 Deliverables) — R2-B2
Date: 2026-06-19 · Workstream: R2-B2-MACRO-2-OWNER-DECISION-PREREQ-CLOSURE-READINESS-2026-06-19 (Deliverable 36 of 45) · Editorial revision: rev1
Class: next-macro (Macro-3) scale plan · 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.
Scale-plan lock. Plans Macro-3 (45–60 min) without fragmenting work or pre-deciding the Owner's choice. It authorizes no macro and opens nothing.
0. Status and non-authorization
STATUS: PASS — engineering / design-only. The Macro-3 plan, scaled and branched by the Owner's Macro-2 decision. It authorizes no macro.
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–35. Reading discipline: main process, no reader-agents.
1. Purpose
Answer macro question 6 — what can be safely bundled into Macro-3 after the Owner decision? — at 45–60 minutes, without fragmenting.
The one rule: scale prompt + deliverable count, never coupling; no tier transitions automatically; the next macro's shape depends on the Owner's Macro-2 decision (it is branched, not pre-decided).
2. Sources / evidence read
The 30-file next-macro scale plan; the Mega-Gate Next-3 roadmap; Deliverables 1–4, 28, 31; the macro §9.5 next-macro sizing. Read directly, main process.
3. Accepted baseline (carried)
Roadmap: Macro-1 (read-only re-verify, done) → Macro-2 (this, channel/Đ0-G/S2 decision-prep) → Macro-3 (staging build readiness → separate build gate) → (separate gate) actual B2 TD. Anti-fragmentation: a larger macro is fine if every deliverable stays a separate, discardable control surface.
4. Macro-3 plan (branched by the Owner's Macro-2 decision; Owner-gated, not authorized here)
| If Owner (Macro-2) … | Then Macro-3 (recommended shape) | Size |
|---|---|---|
| Defers / keeps read-only | another read-only/decision-prep macro (deepen the three ballots; fresh-readonly re-verify; refine proof obligations) | 45–50 deliverables (still read-only/decision-prep) |
| Decides the three prerequisites (channel/Đ0-G/S2) | staging build readiness deepening (Path 5) — NT/DF proof design, IO-contract hardening, no-touch baselines — still readiness-only, no build | 30–40 deliverables (if live-readonly checks are heavy) |
| Authorizes a write-enabled step later | a separate actual-B2-TD-entry macro behind its own gate (never bundled with decision-prep) | separate gate; not sized here |
Sizing rule (macro §9.5): 45–50 if still read-only/decision-prep; 30–40 if live-readonly checks are heavy; no smaller fragmented prompts unless a safety lock triggers. No coupling: each Macro-3 deliverable remains a separate control surface; no automatic planning→TD→impl.
Macro-3 must NOT: select a channel, assign an owner, adopt a source, write actual TD, build staging, expand B5/B7, or open R1/KG — unless the Owner has explicitly decided those outside the macro.
5. Result
Macro-3 is planned, branched, and Owner-gated — not authorized. Its shape follows the Owner's Macro-2 decision; default is another read-only/decision-prep macro at 45–50 deliverables. OWNER_DECISION_REQUIRED.
6. Owner-gated future work
Authorizing and shaping Macro-3 is the Owner's act (after the Macro-2 decision); forbidden now.
7. What remains unresolved
- Macro-3 planned, not authorized; its branch depends on the Owner's decision.
- Blockers — all OPEN.
8. Ready for GPT/Codex review
Yes — as the Macro-3 scale plan.
Core rule: Macro-3 is branched by the Owner's Macro-2 decision (45–50 read-only / 30–40 live-readonly / separate TD gate); scale not coupling; no macro authorized.
Default disposition: HOLD. Engineering PASS ≠ authority PASS. All blockers remain OPEN.