16 — UI / Operator Implications + Governance/Authority Interaction

What the UI MUST show (from v_rp_ui_source_reality_contract)

• Counts trusted as exact: the 15 COVERED sources + governance/pivot metadata, all fresh ≤26h.
• PARTIAL badge required: kb_sop_docs (2, subset only), host_trigger_classes (77, host-only), process_observations (15, thin/REAL_RUN-off).
• UNKNOWN (never 0): ui_route_package_source — show "UI not deployed", count NULL.
• Trigger panel: "602 triggers (525 DB + 77 host); 0 RP-visible until AX-TRIGGER canon". Never "0 triggers".
• Scanner freshness: read from wf_adapter_run_log (last run 2026-06-05 02:10), NOT wf_scanner_run_log/workflow_scanner_registry (frozen 06-04 — provenance lie).
• Drift badges: dot_tools cron (35 declared-not-scheduled), 101 fs-no-registry, trigger_registry stale.
• Action queue: 7 EXECUTABLE safe-triage + 132 HANDLER_READY; 15 owner-blocked; 7 authority-blocked.

The RP UI itself remains undeployed (feat/rp-current-supervision @ d04d8e5, operator git push — unchanged this run). These contract views are consumable the moment it deploys; no Nuxt-side math required.

Governance / authority ownership map

issue	owner	unblocks
AX-TRIGGER registration	president + axis owner	602 triggers become RP-visible
official AX-PROCESS RP (PROC-OWN-01..05)	president vote	official process RP > 0
kb_sop full crawl	operator	KB coverage PARTIAL→COVERED
REAL_RUN flip	authority	run evidence; real_actuation score
35 cron drift / 101 fs orphans / trigger_registry	object owners	drift→OK, dot coverage→complete
scanner provenance wiring	T1 (safe host edit)	freshness tables stop lying
UI deploy / repoint	operator	UI live; generator backbone (optional)

Which gaps block officialization vs are only UI warnings: AX-TRIGGER, PROC-OWN votes, and REAL_RUN block officialization (authority). kb_sop partial, host-only triggers, cron drift, fs orphans, provenance lie are UI warnings / safe-eng reconciles — they do not block, they must be shown.