v_qt001_26a_fix4_no_bypass_proof enumerates every chain from current state to apply and confirms each blocked (11/11): writer_direct_call_execute (readiness v7 not ready + no-legacy + fingerprint v4 + tier apply_allowed + signoff v4); writer_reads_legacy_readiness (writer free_of_legacy); builder_emits_v2_plan (authoritative path legacy-free); current_plan_v2_hash (CURRENT is v4 composite); tier_promoted_via_old_signoff (tier signal v4 only); tier_promoted_via_invalid_block (invalid BLOCK blocks fail-closed); random_reviewer_or_approver (spoof tests 5/5); fake_capability_proof (fake-capability tests 3/3); null_fingerprint_component (scale not safe + NULL detected); directus_dml_path and public_execute_path (structurally blocking via readiness SSOT; REVOKE routed 2.6B).

bool_and(blocked)=true, 0 open. The writer/driver are the only objects that can birth, and both fail closed before any INSERT. There is no path from current state to a QT-001 apply.