Owner / President Decision Playbook

2026-06-04. The decisions only you can make, and exactly what each unblocks.

Why this exists

Every engineering branch is closed. The remaining blockers are authority only. This is the complete decision list.

Decision set 1 — Process Axis (PROC-OWN, human-president approve votes)

vote	unblocks	effect
PROC-OWN-01	axis owner	governance_object_ownership(axis:AX-PROCESS)
PROC-OWN-02	axis canon	axis_registry id 4 → ACTIVE
PROC-OWN-03	job:cut official	axis_assignment row; official RP 0→1
PROC-OWN-04	dot:kg family owner	enables dot:kg REAL_RUN ladder + 10-split
PROC-OWN-05	event activation	7 process.* event types active

Order: 01 → 02 → {03, 05}; 04 parallel after 01. Verify with fn_pa_post_vote_dryrun() and v_process_axis_officialization_sequence.

Decision set 2 — Trigger Axis (TRIG-OWN, when ready)

TRIG-OWN-01 assign AX-TRIGGER owner → TRIG-OWN-02 canon axis_registry(AX-TRIGGER) → TRIG-OWN-03 confirm 69 relations → TRIG-OWN-04 retire 27 stale triggers. Spec in v_ax_trigger_canon_prep_spec.

Decision set 3 — Runtime authority

• Flip process_dot_runtime.{dry_run_only,execute_enabled,real_run_enabled} for dot:kg REAL_RUN (run v_dotkg_realrun_preflight first).
• UI deploy: resolve web-test.git divergence (ahead 17/behind 13) and ship the process-axis dashboard.

What the agent will NEVER do

Cast a vote, assign an owner, write canon, activate an event, enable REAL_RUN, or deploy over the public repo. Those are yours by construction (fail-closed handlers + human-only gates).