Supertrack I — Control-Plane P0 Dashboard & Next-Macro Router

Live P0 status dashboard (v_control_plane_p0_status_dashboard)

rank	domain	status	owner	key metric
1	oom_incident	GREEN	none	landmines=0; no signal-9 since 2026-06-05 06:04 UTC
2	authority_bypass	AMBER	agent(P1)+owner(ratify)	insert-bypass CONTAINED; scanner auto-apply ungated; no apply-time quorum re-proof
3	birth_policy	GREEN	platform/owner (packet)	8/8 clean cycles; h11a=CONTAINED; dup_trigger packet=18
4	object_raw_truth	GREEN	operator (UI, optional)	managed=2,929 vs raw=1.21M (98.97% noise, accounted)
5	trigger_registry_gap	AMBER	owner/operator	408 live / 107 registered / 301 candidate; 83 P1 unmanaged mutating
6	function_permission	AMBER	owner/operator	598 funcs / 38 SECDEF+PUBLIC; 35 staged REVOKEs
7	rp_api_ui	RED	operator/dev	page 200; 404 registries/index; 500 matrix+pivot-query; 14 PIVOT_MISSING
8	dot_metadata_gaps	NOT_ASSESSED	agent (future)	deferred this session
9	final_acceptance	BLOCKED	all	depends on ranks 2,5,6,7

Counts: 1 RED, 3 AMBER, 3 GREEN, 1 NOT_ASSESSED, 1 BLOCKED.

Router (v_control_plane_next_macro_router)

• next_domain: authority_bypass
• next_macro: AUTHORITY_P1_HARDENING_AND_BACKAUDIT_RATIFICATION — gate auto_apply_approval() behind a vote/quorum; add an independent quorum re-proof at approved→applied; ratify the 21 applied-without-quorum rows and reconcile APR-0234 (owner/president votes).
• primary_owner: agent (P1 hardening) + owner (ratification votes)
• top_operator_macro: TRIGGER_REGISTRY_REGISTRATION_OWNER_PACKET (highest-rank operator-owned open item; RP_PRODUCTION_API_OPERATOR_FIX is the RED parallel track for dev)
• posture: MONITOR_WITH_GUARDS — foundation P0s contained; route strictly by the fixed priority (OOM > authority > birth > object > trigger > permission > rp-api > dot > final), not by habit.

The router faithfully follows the macro's fixed priority. Because OOM is GREEN and authority is the lowest-rank non-green domain (P0 contained but P1 open), the next agent-doable macro is authority hardening; the RED rp_api_ui is surfaced as the top operator/dev defect in parallel.

The router view re-evaluates the dashboard (which touches the pivot contract) and runs in ~25 s — read it via ssh … statement_timeout=0, like the other deep RP dashboards.