08 — AX-PROCESS Pivots / Canon Path + UI Deploy Packet (Workstreams G + H/UI)

Canon path (PIV-340..353)

• axis_registry.AX-PROCESS = CANDIDATE; v_axis_process_pivots = 14 (PIV-340..353), all CANDIDATE.
• Canon insert effect: AX-PROCESS → ACTIVE plus 14 unretirable PIV births in pivot_definitions.
• Owner gate: PROC-OWN-02 (register_axis, high-risk, handler unimplemented).
• AI review: AX-PROCESS = AI_REVIEWED_PASS → SEND_TO_GOVERNANCE; PIV-340..353 = AI_REVIEWED_PASS → SEND_TO_GOVERNANCE.

Decision: STAGED CANON (recommended)

Rather than one 15-birth commit: (1) canon AX-PROCESS axis first (1 admission), (2) canon PIV-340..353 second (14 births), each behind its own president approval and preview. This bounds the irreversible step and lets the owner stop after stage 1 if desired. Each stage is an action-panel entry with a preview modal.

No vague state

PIV-340..353 now carry an AI review verdict, a recommended action, an irreversible-births warning (14), and a preview path. They are ready_for_owner_action in v_process_axis_review_action_queue.

UI deploy packet (Registries-Pivot)

The frontend is delivered as a patch packet (operator-gated Nuxt build — not live-deployed, to avoid a container rebuild in this run). Routes/components:

• /registries-pivot/process-axis — list from v_process_axis_review_action_queue.
• Evidence drawer — joins v_process_discovery_evidence_graph_v2, v_process_discovery_policy_scan_summary, v_axis_process_governance_gap.
• AI review panel — v_process_axis_ai_review_status.
• Action bar — deliberate buttons from v_process_axis_action_preview (render requires_president as a red lock, ai_delegatable as a delegate chip; never a checkbox).
• Preview modal — calls fn_process_axis_preview_action (read-only) and shows blocked_gates + rollback caveat + exact backend action before any submit.
• Submit path — fn_process_axis_submit_review_action (review) or surfaces the president-gate for execute_guarded_action.
• API: 5 endpoints (preview, submit-review, execute-guarded, delegate-batch, queue-read) — all thin wrappers over the live functions; no business logic in Nuxt.

Operator step: build nuxt-ssr-local with the new routes, deploy behind existing nginx. No schema change required (all backend objects already live).