09 — Registries-Pivot / UI Runtime-Correlation Impact (Workstream H)

9.1 What RP/AX-PROCESS must now show

The discovery engine can now distinguish why a process is not verified. AX-PROCESS should render candidates with their gap reason, not a flat list:

• structural candidate (start+end present) — birth_readiness_v2.readiness_class ∈ {runtime_missing, structural_weak}
• runtime missing — runtime_gaps.runtime_gap_status ≠ RUNTIME_PRESENT
• correlation missing — correlation_gaps.has_cross_component_correlation = false
• event missing — birth_readiness_v2.event_missing = true
• verified candidate — appears in v_process_discovery_verified_candidates
• birth-ready — birth_gate_status_v2 = BIRTH_READY_PENDING_OWNER

9.2 Inventory swap

RP/AX-PROCESS count surface should adopt v_axis_process_inventory_v2 to stop hiding the 18 KG producers (and 28 producer-bearing pairs overall). v1 (v_axis_process_inventory, 60) stays live for backward compatibility until pivots PIV-340..353 are re-pointed; the swap is an operator/owner decision, not a silent cutover.

9.3 API routes (package, PATCH-READY — operator-gated deploy)

All counts/scores computed in PG; no Nuxt math; routes are thin pass-throughs over the views:

• GET /process-discovery/runtime-gaps → v_process_discovery_runtime_gaps
• GET /process-discovery/correlation-gaps → v_process_discovery_correlation_gaps
• GET /process-discovery/verified → v_process_discovery_verified_candidates
• GET /process-discovery/dot-family-pairs → v_process_discovery_dot_family_pairs
• GET /process-discovery/birth-readiness → v_process_discovery_birth_readiness_v2
• GET /process-axis/inventory-v2 → v_axis_process_inventory_v2

Handlers mirror the existing registries-pivot/*.get.ts pattern (select-from-view, return rows). No business logic in the handler.

9.4 UI components (package)

• Candidate card with a gap-reason badge row (runtime_missing / correlation_missing / event_missing / owner_missing), colour-coded by severity.
• Pair coverage strip for DOT families (producer ●/verifier ● per pair, pair_complete highlighted).
• "Why not verified" drawer that lists the four gates and which are unmet, reading straight from birth_readiness_v2.
• Candidates render report-only under AX-PROCESS (PIV-3xx style); official process rows appear only after birth.

9.5 Constraints honoured

• No Nuxt math (PG computes everything). · No fake "official" process. · Report-only candidate surface. · Deploy is operator-gated (Nuxt rebuild); this macro packages, does not deploy.