102 — Phase 1 Next Prompts (paste-ready)

Mission §15 next-macro. Tier: routing. Mutation footprint: ZERO. Each prompt starts from doc 89 + this authorization pack (93–101). None authorizes a COMMIT — a COMMIT prompt is legitimate only when it can quote a live os_proposal_approvals row for the step + the required council record. The default everywhere is rehearsal-only. Common preamble (prepend to each): "Read docs 00, 88, 86, 89, then 93–101. Confirm live os_proposal_approvals (M-1) and the step's council record. Channel: ssh contabo → docker exec -i postgres psql -U workflow_admin -d directus. Set the three timeouts. If M-1 not met or the council record absent → STOP / rehearsal-only. Return doc 89 §89.8 fields."

---

P1 — Obtain authorization (the actual blocker; human/council, not an agent macro)

GOAL: Move M-1 from 0 → 1 for the chosen first Phase-1 step, and record the council decision.
WHO: President (sovereign) writes the os_proposal_approvals row for the step (e.g. "SB-12 build");
  Council records C-1 (if SB-2 first) / C-2 (if SB-1) — silence ≠ approval.
DELIVERABLE: a live os_proposal_approvals row scoped to ONE step + the council record id.
NOTE: no agent/GPT may create these. This is the only thing standing between rehearsed-green and build.
RECOMMENDED FIRST STEP (per GPT review + doc 93): SB-12 + SB-13 — cleanest greenfield foundation, no trigger/birth complexity.

P2 — Pre-authorization rehearsal refresh (runnable NOW, rehearsal-only)

GOAL: Re-run the BEGIN..ROLLBACK rehearsal for the next-to-build step to re-prove entry==exit on TODAY's live state
  before any authorization arrives. Use doc 95 §95.9 NO-GO/rehearsal-only form + doc 99 file structure (terminal ROLLBACK).
STEPS: pick SB-12 (or SB-13/SB-10/SB-11/SB-2/SB-1) per doc 93 order. Apply the step's doc-86 fold-ins.
PROVE: target ABSENT→ABSENT (greenfield) / apr_action_types 6→6 (SB-1); event_outbox governance=0; idle_in_tx=0.
FORBIDDEN: COMMIT; any persistent object; emit; approval row.
REPORT: doc 89 §89.8 with COMMIT=no; "ZERO COMMIT, entry==exit, rehearsal-only."

P3 — First build step (ONLY if authorized; one step, one COMMIT)

GOAL: Build the single authorized first step (recommended SB-12) per doc 94 + doc 99 file (build variant).
PRECONDITION (quote evidence): os_proposal_approvals row id for THIS step (M-1) + council record if required.
  If absent → run as P2 rehearsal-only instead.
DO: doc 96 preflight → BEGIN+GUC → doc-86 fold-ins → additive DDL (from the design doc) → in-txn verify+negatives
  → pg_dump → COMMIT → doc 101 post-step verification.
FORBIDDEN: batching a second step; activation/emit; DOT; Phase-B handler; governance_relations ALTER.
STOP: any doc 96 §96.5 condition.

P4 — SB-1 build step (ONLY if authorized; carries F-83-1)

GOAL: Build SB-1 (STEP 6) per doc 94 §94.7 + doc 98 (F-83-1) + doc 99 06_sb1 file.
PRECONDITION: os_proposal_approvals (SB-1) + council C-2. Else rehearsal-only.
MANDATORY: F-83-1 trigger re-wire to fn_birth_registry_auto('action_code') BEFORE the 4 INSERTs (doc 98 §98.3).
PROVE: apr_action_types 6→10; birth_apr rows 0→4 (entity_code=action_code, no phantom); approval_requests/apr_approvals unchanged;
  TRIGGER-GUARD is WARNING not ERROR.
FORBIDDEN: flip handler_ref; create approval_requests row (esp. action='add'); emit.
ROLLBACK: in-flight ROLLBACK; post-commit RETIRE rows, KEEP the trigger fix (doc 98 §98.5).

P5 — Post-build verification + hold (after any committed step)

GOAL: Run doc 101 (per-step slice, or full sweep after the last step) and confirm Phase-1 quietness.
ASSERT: event_outbox governance=0; no unauthorized approval/DOT/law/surface change; scanner inactive;
  candidate state empty; idle_in_tx=0. Record the delta vs doc 96 baseline.
THEN: HOLD (doc 94 STEP 7). Do NOT start T6/T7/backfill/DOT/activation — those need a new macro + new gates.

P6 — GPT review of this authorization pack (recommended before any build)

GOAL: Have GPT review docs 93–103 for completeness/safety before authorization is sought.
CHECK: scope correct (substrate spine only); transaction strategy (per-step) sound; F-83-1 handling (doc 98) correct;
  GO/NO-GO matrix (doc 100) consistent with 87/88; no implementation disguised as authorization.
OUTPUT: PASS / changes-needed; if PASS, GPT may recommend the first step to authorize (default SB-12+SB-13).

P7 — Future-phase design (NOT Phase 1; design-only)

GOAL: When Phase 1 is built + verified, design Phase 2: T6/T7 addenda build (doc 24/25/69 fold-ins, tier-A only),
  GCOS backfill dry-run (C-7.3), event activation (C-7.1), production gate (G-PROD).
PRECONDITION: SB-10..13 + SB-2 + SB-1 built and verified. Still NO G-APPLY (A-9).
MODE: design/authorization-pack, same discipline as docs 93–101. No build.

---

102.1 Recommended sequencing

P6 (GPT review of 93–103)  →  P1 (sovereign/council authorization, SB-12 first)
  →  P2 (refresh rehearsal)  →  P3 (build SB-12)  →  P5 (verify)
  →  repeat P1→P3→P5 per step in order SB-12 → SB-13 → SB-10 → SB-11 → SB-2 → SB-1(P4)
  →  P5 full sweep + HOLD  →  P7 (Phase-2 design, later)

The binding next action is P1 (authorization). Everything engineering is already done; P2/refresh and P6/review are runnable now without any authorization.

Branch verdict: next prompts are routed — authorization (P1) is the real blocker; rehearsal refresh (P2) and GPT review (P6) are runnable now; build prompts (P3/P4) and verification/hold (P5) are gated on M-1 + council records; Phase-2 design (P7) is later. No prompt authorizes a COMMIT; M-1=0 ⇒ all build prompts resolve to rehearsal-only.