KB-61D4

FIX4 05 — Tier Signal + Signoff v4 Only

1 min read Revision 1

Chain: fn_qt001_machine_tier (wrapper) -> fn_qt001_machine_tier_v4 -> fn_qt001_eval_rule_v4 -> fn_qt001_collection_signals_v4 -> fn_qt001_signoff_satisfies_v4. No old signoff anywhere in the tier path.

fn_qt001_machine_tier_v4 is FAIL-CLOSED on BLOCK: a BLOCK rule blocks the tier unless fn_qt001_eval_rule_v4 returns exactly 'BLOCK_CLEAR'. A governance-invalid BLOCK returns 'NOT_PARTICIPATING_GOVERNANCE' (<> BLOCK_CLEAR) and therefore BLOCKS — it can no longer be ignored to promote a tier.

Guards: v_qt001_tier_signal_v3_only_guard pass true (wrapper_uses_v4, eval_uses_v4_signals, signals_use_signoff_v4, no_old_signal_path). v_qt001_block_rule_governance_error_guard pass true (fail_closed_block_present, no_fail_open_block_test).

Tier distribution through the v4 authoritative path reproduces FIX3 exactly: TIER2=7, TIER3=6, TIER_BLOCKED=6, TIER_INELIGIBLE=55, TIER1=0 — proving the repoint changed the routing of authority, not the governed outcome.

Back to Knowledge Hub knowledge/dev/reports/architecture/birth-stage2-6a-fix4-qt001-authoritative-path-repoint-no-legacy-bypass-2026-06-07/05-tier-signoff-v4-only.md