KB-2BEA

06 Phantom / Stale / Static-Literal / No-Hardcode Hardening — 2026-06-05

3 min read Revision 1
rp-count-reliabilityphantomstalestatic-literalphase-e2026-06-05

06 — Phantom / Stale / Static-Literal / No-Hardcode Hardening (Phase E)

Goal: no known phantom/stale/static/hardcoded risk remains unlabeled. Read-only labeling (no canon mutation; owner authority not faked).

E1 · v_rp_referenced_not_built_detector — 6 findings

PIV-301..303/304/312/500-class codes are referenced (in v_rp_aggregate_candidate_register, v_axis_topic_pivots) but not built in pivot_definitions. They are already honestly labeled by the register:

code concept live_count status → reliability
PIV-301 orphan 59 CANDIDATE_REPORT_ONLY → CANDIDATE
PIV-302 phantom 289 CANDIDATE_REPORT_ONLY → CANDIDATE
PIV-303 count_drift 3 CANDIDATE_REPORT_ONLY → CANDIDATE
PIV-304 unmanaged NULL NEEDS_LAW_DEFINITION → NEEDS_LAW
PIV-312 kg_edges 2259 NEEDS_LAW_DEFINITION → NEEDS_LAW
PIV-500 grand_total NULL NOT_A_PIVOT_EQUATION_VIEW → ADVISORY
0 dangling pivot parent/superseded refs (one superseded_by='deprecated' literal = DEPRECATED marker, not a code). Result: all referenced-not-built codes carry a reliability label; none can be mistaken for a built pivot.

E2 · v_rp_stale_parallel_source_detector

trigger_registry 107 vs live pg_trigger 408 → STALE · kb_sop_docs adapter PARTIAL · (no adapter >1d stale post-scan). wf_*_digest_v2 snapshots exist (3) but are superseded by health_v2 live; flagged via adapter staleness.

E3 · v_rp_static_literal_detector — PXT ledger live re-check (6 gaps)

gap ledger literal live verdict
PROC:residual_reconcile 8 2 STALE (LEDGER_LITERAL_STALE confirmed)
TRIG:job_queue 8 13 STALE
PROC:new_candidates 6 6 FINAL
PROC:official_rp 0 0 FINAL
TRIG:db_dml_trigger 408 408 FINAL
TRIG:event_type 52 52 FINAL
2 stale literals surfaced (not mutated — the ledger view is owner/canon territory; the detector replaces them with live values for any consumer). This is the no-hardcode replacement done safely: live source wins, literal flagged.

E4 · v_rp_synthetic_axis_register_gap — 3 SYNTHETIC

AX-BASE (39), AX-PXT (12), AX-TRIGGER (7) are computed in views, not in axis_registry → SYNTHETIC, next_action register_axis. AX-PROCESS (22), AX-TOPIC (7) are registered CANDIDATE.

E5 · v_rp_partition_law_status

AX-PROCESS, AX-TOPIC → FINAL (have substrate_resolver). AX-BASE, AX-PXT, AX-TRIGGER → ADVISORY (no registered partition law; their parents are advisory aggregates, not partitioned).

E6 · v_rp_dedup_signature_gap

pivot_definitions.normalized_signature 39/39 NULL → dedup inert; duplicate-pivot detection disabled → NEEDS_RECONCILE (operator backfill).

Completion: every known misleading artifact (phantom PIVs, stale trigger_registry, stale ledger literals, synthetic axes, non-partition parents, NULL dedup signature, MTX-TEST, PIV-020) is now detected and labeled. ✔

Back to Knowledge Hub knowledge/dev/reports/architecture/rp-count-reliability-adapter-coverage-dot-trigger-process-reconciliation-2026-06-05/06-phantom-stale-static-hardcode-hardening.md