Registries-Pivot — Process Coverage Legend

How to read the AX-PROCESS coverage badges and numbers. Counts come from PG views, never computed in the app.

Badge colors

• 🔴 Official (canon) — assigned to AX-PROCESS via axis_assignment. Today: 0 / 453. Red = owner-gated, not an error.
• 🟡 Candidate-visible — recognized as a candidate, listable, not yet official. Today: 69 host objects / 19 candidates / 17 clusters.
• ⚪ Not-process — OS-level, shared lib, template, run-once infra, noise. Excluded by design.

Status words on the canon-gate screen (v_rp_process_canon_gate_summary)

Status	Meaning
OPERATIONAL	RP can list it now
BLOCKED_OWNER	needs a human owner/president decision
RESOLVED	hardened with evidence this phase
RESOLVED_ENG_LINK	already managed; only a scanner-link backlog remains
ACCEPTED	accepted as not-process
READY_FOR_OWNER / READY_FOR_PRESIDENT	the decision is teed up

The verdict line

canon_gate_verdict = CANON_BLOCKED_OWNER_ONLY — all engineering is cleared; the only thing standing between candidate and official is owner/governance authority.

Verified badge

Only job:cut shows the verified badge, sourced from the verified view — never inferred client-side.

Reading the denominator

/453 is the full entrypoint universe (373 DB defs + 80 host entrypoints). /143 is the orphan-object scope being remediated. Don't mix the two.