17 · Next Macro Compression (2026-06-05)

Decision

Chosen next macro: FINAL_OFFICIALIZATION_UI_DEPLOY_DOTKG_REALRUN_AND_RP_ACCEPTANCE (option 1).

Rationale (per decision rules)

• No president vote exists yet → the next macro must keep content/UI/dotkg prep in parallel while officialization waits on authority. Option 1 does exactly this: it executes officialization handlers if/when votes appear, deploys UI if operator authority is granted, and otherwise continues all authority-independent verification + acceptance tracking.
• UI branch is ready → include deploy (push/PR/smoke) the moment operator authority lands.
• All authority-independent engineering is done → the next macro is effectively "final officialization + the operator/authority actions," not new engineering. It is final-scale (all axes + dot:kg + RP acceptance), not a small macro.

Why not the others

• Option 2 (UI_PR_DEPLOY_AND_OWNER_OFFICIALIZATION_PARALLEL) — subset of option 1.
• Option 3 (DOTKG_REALRUN_TRIGGER_CANON_AND_INFORMATION_PIECE) — omits UI deploy + AX-PROCESS officialization, which are now the highest-value flips.
• Option 4 (PRESIDENT_VOTE_EXECUTION_AND_ALL_AXES) — assumes votes already cast; they are not.

Shape of the next run

1. Dual-path drift re-audit.
2. If PROC-OWN votes present → execute handlers (official RP, events, dot:kg owner) and verify flips.
3. If UI operator authority present → push/PR/deploy + smoke.
4. If dot:kg config flipped → first correlated REAL_RUN + verify.
5. AX-TRIGGER canon if owner assigned.
6. Re-score acceptance; publish final acceptance checkpoint.
7. Otherwise: continue parallel prep, D11/D14 backlog (host adapters + UI ledger panel), content.