04 — Authority Execution Pack (DO NOT EXECUTE — map only)

This maps the exact action sequence to run IF/WHEN president/owner authority lands. Nothing here is executable by an agent: every path is fail-closed behind a president vote and/or an owner record that are both currently empty. T2 did not execute anything.

Current no-fake state (T2 live cross-check, 2026-06-05 — all confirmed)

• governance_object_ownership = 0 (no owners)
• PROC-OWN requests = 5 (all pending), apr_approvals president votes = 0
• axis_registry = 2 rows, 0 ACTIVE (AX-PROCESS + AX-TOPIC, both CANDIDATE)
• AX-PROCESS official RP = 0; trigger_guard_alerts = 129
• event_type_registry active = 30 (the 7 process.* events remain inactive draft)
• dot_config process_dot_runtime.real_run_enabled = false

The two universal gates (every handler is blocked on these)

• Gate P (president vote): a human-president APPROVE vote must exist in apr_approvals (joined to approval_requests). Currently 0 for all PROC-OWN. Council/non-human votes do NOT satisfy this.
• Gate O (owner record): governance_object_ownership.object_ref must hold the object's owner. Currently 0.
• Handlers fn_pa_handler_{assign_axis_owner, register_axis, register_process, assign_governance_owner, activate_event_type} and fn_wf_candidate_action_execute() all return BLOCKED_NO_PRESIDENT_VOTE until Gate P passes; canon-mutating actions never auto-execute.

PROC-OWN exact mapping (codes/titles verified live; all status=pending, votes=0)

PROC-OWN-01 — axis_ownership

• Title: Assign owner for AX-PROCESS axis (governance_object_ownership empty).
• Action when authority lands: president approves PROC-OWN-01 → fn_pa_handler_assign_axis_owner writes the AX-PROCESS owner into governance_object_ownership.
• Expected RP change: ownership 0 → 1 (AX-PROCESS). UNBLOCKS the rest of the chain.
• No-go: do not run any later PROC-OWN until 01's owner exists.

PROC-OWN-02 — axis_canon

• Title: Canon AX-PROCESS (CANDIDATE→ACTIVE) + canon PIV-340..353.
• Action: president approves → fn_pa_handler_register_axis flips AX-PROCESS to ACTIVE and canons the PIV nodes.
• Expected RP change: axis_registry ACTIVE 0 → 1 (AX-PROCESS); AX-TOPIC stays CANDIDATE.
• Pre-req: PROC-OWN-01 owner present.

PROC-OWN-03 — process_registration (job:cut — the sole verified process)

• Title: Register job:cut process (verified, 8 members) + assign owner + birth admission.
• Action: president approves → fn_pa_handler_register_process registers job:cut as the FIRST official process, assigns its owner, admits its birth.
• Expected RP change: AX-PROCESS official RP 0 → 1 (job:cut, 8 members).
• Pre-req: PROC-OWN-01/02. job:cut is the only CONFIRM_AS_PROCESS-verified candidate.

PROC-OWN-04 — process_family_registration (dot:kg + REALRUN ladder)

• Title: dot:kg family owner + authorize 10-process definition split.
• Action: president approves → assign dot:kg family owner + authorize the 10-process split. SEPARATELY, the REALRUN ladder is gated by dot_config process_dot_runtime.real_run_enabled (currently false). Flipping real_run is an OPERATOR runtime action, distinct from the vote.
• Expected RP change: dot:kg owner set; 10-process split authorized. real_run stays false until operator flips it (dry_run_only true today). dot:kg remains REALRUN_BLOCKED until both the owner lands AND the operator flips real_run_enabled.
• No-go: never flip real_run_enabled without owner + explicit operator authorization.

PROC-OWN-05 — event_activation

• Title: Authorize activation of 7 process.* event types (currently inactive draft).
• Action: president approves → fn_pa_handler_activate_event_type activates the 7 process.* events.
• Expected RP change: event_type_registry active 30 → 37 (the 7 process.* events go active).
• Pre-req: PROC-OWN-01..03 (events describe official processes).

Synthetic-axis registryization (separate from PROC-OWN; from v_rp_synthetic_axis_registryization_packet)

• AX-BASE → REMAIN_DERIVED (remain-derived; no registration needed).
• AX-PXT → CANDIDATE_REGISTER (needs owner + live-ledger refactor). Registering AX-PXT is a pre-req for TRUE no-hardcode decoration (the 58 view-edits) and thus for a clean repoint.
• AX-TRIGGER → REGISTER_IN_AXIS_REGISTRY (needs owner + president register). Currently synthetic, no canon, not in axis_registry. Unlocks the no-hardcode registryization path.
• No insert is staged — these are authority actions, not engineering.

Recommended execution ORDER when authority lands

1. PROC-OWN-01 (owner) — unblocks everything.
2. PROC-OWN-02 (axis canon ACTIVE).
3. PROC-OWN-03 (job:cut first official process).
4. PROC-OWN-05 (activate 7 process.* events).
5. PROC-OWN-04 (dot:kg owner) → then OPERATOR flips real_run_enabled for the REALRUN ladder.
6. AX-PXT register → AX-TRIGGER owner+register → then the no-hardcode repoint (doc 02) becomes available.

• After EACH step: re-run the no-fake cross-check (doc 00) to confirm the intended single delta and no collateral change.

Hard no-go

• No officialization (official RP, axis ACTIVE, votes, REALRUN, event activation) without the matching president/owner authority. Agents cannot and must not fabricate Gate P or Gate O.