KB-3A07

Registries-Pivot Official / Candidate / Trigger Legend

2 min read Revision 1

Registries-Pivot — Official / Candidate / Trigger Legend

2026-06-04. How to read the RP badges and states.

Process states

  • OFFICIAL — has an axis_assignment row. Count today: 0/453.
  • VERIFIED — in v_process_discovery_verified_candidates_v3 (job:cut only). Pending owner.
  • CANDIDATE_VISIBLE — RP can list it; owner UNASSIGNED (11 of 19 WPC).
  • NEEDS_REVIEW — AI flagged more evidence needed (4).
  • NOT_PROCESS — classified out (3 + 42 baseline).
  • OWNER_GATED — docker runtime / unregistered, needs owner (1 + 11).

Trigger states

  • PROCESS_RELEVANT — maps to a process candidate (117 triggers, 6 classes), owner 0.
  • INFRA_NO_PROCESS — db_dml (408), fires on DML, no governed process.
  • STALE_DISABLED — disabled DB triggers (27), retirement candidates.
  • EVENT_INACTIVE — event types active=false (22).

Canon verdicts

  • Process: CANON_BLOCKED_OWNER_ONLY.
  • Trigger: TRIGGER_CANON_BLOCKED_OWNER_ONLY.

Golden rule for the UI

Every number comes from a PG view. No Nuxt math. The badge you see is the badge PG computed.

Back to Knowledge Hub knowledge/dev/content/process-trigger-axis/07-registries-pivot-official-candidate-trigger-legend.md