KB-2F05

Authority P1 Hardening — 08 Control-Plane Router v2

3 min read Revision 1
control-planerouterdashboard2026-06-06

08 — Control-Plane Router v2

P1 status dashboard (view v_control_plane_p1_status_dashboard)

prio lane state
1 oom GREEN
2 authority_p0_containment GREEN
3 scanner_auto_apply_control GREEN
4 apply_time_quorum_reproof GREEN
5 birth_policy GREEN
6 backaudit_ratification AMBER
7 rp_production_api RED
8 trigger_registry AMBER
9 function_permission AMBER

The lane states are live-derived where possible: oom (no signal-9), authority_p0_containment (from v_authority_p0_still_contained_guard), scanner_auto_apply_control (from v_scanner_apply_control_status = CONTROLLED), apply_time_quorum_reproof (from v_apply_time_quorum_reproof_status = IMPLEMENTED). backaudit is AMBER because the 21 ratifications + APR-0234 are action-ready but owner/president-blocked. rp_production_api stays RED (unchanged from the P0 macro: /api/registries/index 404, /api/registry/matrix 500, pivot missing). trigger_registry and function_permission remain AMBER (packets only, unchanged).

Router v2 (view v_control_plane_next_macro_router_v2)

Routing priority (macro order): OOM incident → authority P0 regression → scanner auto-apply risk → apply-time quorum gap → birth policy regression → RP API/UI broken → trigger registry/permission hardening → final acceptance.

Result: the first five priorities are GREEN. The first non-green by priority is rp_production_api (RED).

  • next_macro = RESOLVE_RED:rp_production_apiRP_PRODUCTION_API_OPERATOR_FIX.
  • top_technical_or_authority = RP_PRODUCTION_API_OPERATOR_FIX.
  • pending_authority = BACKAUDIT_RATIFICATION (president/owner) + APR-0234 reconcile (president).
  • red_lanes = 1, amber_lanes = 3, green_lanes = 5.
  • posture = MONITOR_WITH_GUARDS.

Interpretation

The authority control-plane P1 work is closed at the engineering layer (lanes 2–4 GREEN). The remaining RED is the RP production API, which is an operator/dev fix, not an authority problem. The remaining AMBERs (backaudit, trigger_registry, function_permission) are all human-authority or owner-packet items with no engineering blocker. Therefore the recommended next macro is the RP production API operator fix, run in parallel with collecting president/owner authority for the ratification queue.

Back to Knowledge Hub knowledge/dev/reports/architecture/authority-p1-hardening-backaudit-ratification-scanner-apply-control-2026-06-06/08-control-plane-router-v2.md