Registries-Pivot — Official vs Candidate Legend

2026-06-04 · how to read coverage badges on the Process Axis UI without being misled.

The core distinction

A process can be visible (the system knows about it) without being official (governance has canonised it under an owner). The UI must never conflate the two. Today:

• Official AX-PROCESS RP = 0/453 — zero processes are canon.
• Candidate-visible = 69 — listed in the candidate layer, not official.

Badge legend

Badge	Meaning	Source
🟢 OFFICIAL	canonised: axis_assignment row with non-null approval_ref	axis_assignment
🟡 CANDIDATE	discovered + AI-reviewed, awaiting owner gate	wf_process_candidate
🔵 NEEDS_REVIEW	AI flagged NEEDS_MORE_EVIDENCE	ai_review_state
⛔ OWNER_GATED	blocked pending president/owner authority	v_..._owner_decision_flow
⚪ NOT_PROCESS	triaged out (not a process)	triage

Coverage buckets (live)

candidate_visible 69 · not_process 40 · owner_gated 11 · needs_review 23 (+373 DB defs).

Anti-misleading rules for the UI

1. No Nuxt math. Every count comes from a committed PG view; the page renders verbatim.
2. Verified ≠ official. job:cut is VERIFIED but still 🟡 until PROC-OWN-03 is voted.
3. 0/453 is shown honestly — the headline official count is zero and the UI says so.
4. Actions are render-only. No checkbox writes; execution goes through guarded fail-closed server functions.

Canon verdict strip

The header shows v_rp_process_canon_gate_summary → CANON_BLOCKED_OWNER_ONLY: all engineering is cleared, only owner/governance authority remains. This is the single most important status line.