KB-7AD3

FIX4 04 — Builder + Current Plan -> Fingerprint v4

2 min read Revision 1

fn_qt001_build_plan_registry repointed: v_fp := fn_qt001_plan_fingerprint_v4(); validation signal via fn_qt001_collection_signals_v4; tier via fn_qt001_machine_tier(->v4); tier_source RULE_ENGINE_V4. CURRENT plan rebuilt so every CURRENT row carries the v4 composite 32a807b7a438cd515fbc1054983ebb64 (was v2 9bac30375765).

fn_qt001_plan_fingerprint_v4 is ACYCLIC and NULL-STRICT: per-binding signoff content removed from the composite (replaced by the controlled-identity-registry content hash) so adding a signoff no longer self-invalidates it; scope components emit literal 'NULL' instead of COALESCE-to-0, and null_component_rows is surfaced (currently 6, all ineligible collections).

Guards: v_qt001_current_plan_fingerprint_authority_status current_is_v4 true; v_qt001_no_v2_plan_hash_guard pass true (current_rows_not_v4=0); v_qt001_null_fingerprint_component_guard pass true (0 eligible rows with NULL control truth). Any plan carrying a v2 hash or any eligible NULL component would fail these and block readiness.

Back to Knowledge Hub knowledge/dev/reports/architecture/birth-stage2-6a-fix4-qt001-authoritative-path-repoint-no-legacy-bypass-2026-06-07/04-builder-current-plan-v4.md