— 09 CONTROL-PLANE ROUTER UPDATE

Before: control-plane router RED lane = RP production API (API_BROKEN: 404 registries/index + 500 matrix + 500 pivot-query, PIVOT_MISSING 14).

After this macro (DB truth, live read-back):

• v_rp_production_ui_no_false_green_guard: verdict BLOCKED_REAL_API_BREAKS_PRESENT_DO_NOT_CLAIM_READY, real_break_routes=3, healthy=12. (Truth holds until the operator deploys; the guard is the gate.)
• v_rp_pivot_missing_no_false_green_guard: verdict PASS_ALL_PIVOT_MISSING_EXPLAINED (14/14 explained). PIVOT_MISSING is closed as understood/contained, not a break.
• v_rp_production_api_router_v2: rp_lane_status = RED_RP_PRODUCTION_API_ACTION_READY_AWAITING_OPERATOR_REBUILD_RESTART; api_real_breaks=3; next_action = operator rebuild .output + restart incomex-nuxt.

Lane transition recorded: RP_PRODUCTION_API moved from RED / API_BROKEN (no path) to RED / ACTION_READY (engineered, proven, staged) — the breaks are no longer unexplained or unfixed; only the operator restart/rebuild remains. The router does not flip to GREEN because no production deploy occurred and the live endpoints are still 500/404; flipping early would be a false green. The guard is wired so that the moment the operator deploys and the endpoints return 200, real_break_routes -> 0 and rp_lane_status -> GREEN_RP_PRODUCTION_API_FIXED automatically (the views are live-derived, not hardcoded).

Post-fix next lane (per program router v2): with the RP production API lane converted to ACTION_READY and the authority/birth/truth lanes already green, the next RED/AMBER macro after the operator deploy is RP UI productionization / clean-vs-raw count truth and the species-matrix slow-route hardening (same pg-aggregate pattern as the matrix fix). These are AMBER, not RED.

The router reflects truth: it neither hides the still-broken live endpoints nor overstates readiness; it encodes the exact remaining blocker (operator restart/rebuild) and will self-correct on deploy.