11 — Pre-Activation Control Tower (Branch K)

No activation executed this session (authority NOT_FOUND, doc 01). This is the pre-activation control tower.

1. Exact next HUMAN action (pick one to open the window)

• Path α (machinery-first, recommended): Sovereign enacts G2 Đ37-H (doc 03) → council deploys G3 proposal/approve path (doc 04) → with G3 live, mint G1 Đ32 cross-sign ≥2 + CR law clause and run the G1 birth (doc 02) → authorize + run G4 flip (doc 05).
• Path β (G1-direct): Sovereign enacts CR law clause + acts as one of ≥2 Đ32 cross-signers directly → run G1 birth (doc 02) now; G2/G3/G4 follow.

2. Exact next AGENT action (only after the human window)

• After G1 born: run Phase-0 config-only first-draft commits (doc 06) inside BEGIN..ROLLBACK-proven, owner-clear inserts; re-run fn_phase0_cockpit() + no-double-ownership verifier (doc 12 group 12).
• After G4 active: re-prove the can_create partition; do NOT open any runtime gate.
• Anytime now: run IU Pilot Day 1 read-only (doc 07) on a cadence; commit cockpit-hardening views (doc 08) if a privileged session is available.

3. Safe stopping point

NOW. Gate all_safe=true, never_flip intact, 0 idle-in-tx, entry==exit counts, no open work. Nothing must be left running.

4. Go/No-Go for config-only implementation

• NO-GO to commit config-only drafts until G1 registries are born (they reference field/input_form/tier which don't exist).
• GO to dry-run config-only drafts now (doc 06) and to prepare exact INSERT shapes.

5. IU Pilot recommendation

• GO for IU Pilot Day 1 read-only now. Run the doc-07 checklist daily. Do not create persisted pilot rows unless owner table + reversal are clear (deferred this session).
• Stop conditions: any gate flips unsafe, DLQ > 0 unexpectedly, idle-in-tx appears, or cockpit counts drift without an authorized cause.

6. Dependency one-liner

G2 → G3 → G1(+Đ32) → G4, with config-only commits unlocking at G1 and factory operability at G4; runtime + UI remain NO-GO behind separate governed gate-open protocols.