14 — Next Macro Decision (2026-06-04)

Decision rules applied

• No president vote exists → do NOT pick officialization-only macro.
• UI still blocked (diverged git) → must include UI PR/deploy.
• Content can proceed in parallel → include.
• Keep macro large.

Chosen next macro

INFORMATION_PIECE_DOTKG_REALRUN_TRIGGER_CANON_AND_FINAL_RP_ACCEPTANCE (option 2), executed in parallel with UI_DEPLOY_PR_BRANCH (option 4) work — because both remaining engineering-adjacent tracks (UI rebase/PR and content/IP expansion) can advance without president authority, while the officialization chain waits on the human-president vote drain.

Scope of next macro (parallel tracks)

1. UI track (operator-assisted): drive the rebase+PR of nuxt feature branch over diverged main → registries-pivot RP UI live.
2. Content/IP track (no authority): expand Information-Piece content (D11–D17), publish RP final-acceptance guide to operators.
3. dot:kg readiness track: keep REAL_RUN preflight current; prepare contract promotion artifacts (no flip without owner).
4. Trigger canon prep track: keep AX-TRIGGER substrate current; trigger-owner packet ready.
5. Officialization standby: the instant PROC-OWN votes land, execute the guarded 01→02→03→04→05 chain.

Rationale

This keeps the macro large and productive while honoring that the single highest-leverage unlock — the human-president vote — is outside engineering control. Every other branch continues.