KB-4B0A
01 — Dual-Path Baseline
2 min read Revision 1
rpdual-pathbaseline2026-06-05
01 — Dual-Path Baseline (Phase 1)
Verified via query_pg (read-only role) and ssh→docker→psql (statement_timeout disabled for composite views). Headline identical on both paths.
Baseline metrics (matched SSOT)
- Contract current guard: verdict PASS, blocker NONE, row_count 87 = expected 87, null route/action/reliability/count 0, invariant real-fail 0, expected-blocker 4, static stale 0, alias 7/7 valid, stale-v1 binding 0.
- Current contract rows 87; generated (v1) rows 84.
- Generator validation summary (v1): 5 axes, 3 parity-pass, 2 gap; membership gap contract-minus-gen 3, gen-minus-contract 0; count diffs 1; safe_to_generate true, safe_to_replace_v1 false; verdict GENERATOR_PREVIEW_SAFE__PARITY_GAP_BLOCKS_REPLACE; full-text md5 2a9c1f00f788bd3509df7512642a9829.
- Invariant v2: 83 PASS + 4 PASS_EXPECTED_BLOCKER + 0 FAIL.
- Smoke probe 15/15; anti-false-green 6/6.
- birth_registry 1,200,161 (SSOT 1,200,159 + 2 background).
- No-fake: axis_registry 2 (0 active), ownership 0, trigger_guard 129, axis_assignment 25.
Conclusion
No mismatch between paths and no drift from SSOT. Safe to proceed with generator parity remediation. The two gaps confirmed live: AX-PROCESS membership 3, AX-PXT count 1.