04 — Guarded Canon / Axis-Assignment

Verdict: official AX-PROCESS RP stays 0/453. Authority to flip it does NOT exist. Not faked.

The four independent gates — all CLOSED (each proven live)

1. Axis is not canon. axis_registry.AX-PROCESS.status = 'CANDIDATE', approval_ref = NULL, owner_governance_ref names GOV-MOW "pending Dieu-XX app-layer ratification". An axis_assignment against a non-canon axis would be fake official visibility.
2. No owner assigned. governance_object_ownership has 0 rows for AX-PROCESS or any process object. ASSIGN_OWNER action handler = unimplemented.
3. No president vote / approval. PROC-OWN-01 (assign owner) and PROC-OWN-02 (canon) are both status=pending. trg_apr_quorum_check requires a human president vote that does not exist; AI cannot cast it.
4. No delegated authority. process_axis_delegation = 0 rows; delegator_type CHECK = human only. There is no standing delegation that would let an agent proceed.

What an official flip would require (the guarded path, in order)

PROC-OWN-01  human president vote  → assign AX-PROCESS owner          (governance_object_ownership +1)
PROC-OWN-02  human president vote  → axis CANDIDATE→ACTIVE + canon     (axis_registry.status=ACTIVE, approval_ref set)
  ↓ only now is the axis a legitimate target
per confirmed candidate: owner confirm → president birth (+1 birth) → governance canon
  ↓
INSERT axis_assignment(axis_code='AX-PROCESS', target=<born process>, status=approved, approval_ref=<APR>)
  ↑ THIS is the single step that makes official RP > 0

Every prerequisite is a human decision. The engineering to execute each step is built and fail-closed; nothing here is blocked on code.

What was NOT done (and why that is correct)

• No axis_assignment written → would be fake official visibility on a candidate axis.
• No APR approved / no president vote simulated → forbidden; AI cannot self-grant.
• No birth → premature without owner + canon.
• No event activation → PROC-OWN-05 still pending.

Candidate surface preserved

The candidate layer (v_ax_process_candidate_*) remains the RP's operational view: RP can list 69 candidate-visible objects, 19 candidates, 17 clusters, and the owner-decision flow — all clearly marked candidate, never official. The OfficialVsCandidateCoverageBadge enforces the visual distinction (official 0/453 red, candidate amber).

Classification: BLOCKED_OWNER_GOVERNANCE. Exact next action = PROC-OWN-01 then PROC-OWN-02 (human president quorum).