fn_dot_birth_qt001_apply execute path repointed (CREATE OR REPLACE; defaults preserved). It now: (1) requires v_qt001_writer_no_legacy_dependency_guard.pass; (2) requires v_qt001_apply_readiness_guard_v7.overall_ready; (3) verifies CURRENT plan source_metadata_hash == fn_qt001_plan_fingerprint_v4()->>'composite' (rejects stale/v2); (4) derives tier via fn_qt001_machine_tier (->v4); (5) requires fn_qt001_signoff_satisfies_v4(collection,tier); then gateway/Stage0/permit/expected-delta/max-rows/false-done gates unchanged. It no longer reads v_qt001_apply_readiness_guard_v5 or fn_qt001_signoff_satisfies(old).

v_qt001_writer_authoritative_repoint_status: pass true; reads_readiness_v7 true; reads_signoff_v4 true; checks_fingerprint_v4 true; checks_no_legacy true; free_of_legacy true.

Negative behaviour: with no REVIEWER identity, no open permit, no apply_allowed tier, and readiness blocked, the writer fails closed on the first execute gate. sp_dot_birth_qt001_apply calls the writer and inherits every gate (no bypass).