08 — Readiness v8 (BLOCKED for structural reasons)

v_qt001_apply_readiness_dashboard_v8 (15 SSOT + 4 APPLY gates, clean guards only) → v_qt001_apply_readiness_guard_v8.

LIVE: overall_ready=FALSE, SSOT 13/15 green, APPLY 0/4 green, reason BLOCKED_STAGE2.6A_FIX5_6_GATES_RED.

SSOT gates (13 green): no_legacy_authoritative_dependency, no_legacy_planner_v2, planner_v2_sentinel_only, current_plan_fingerprint_v5, no_v5_plan_hash, null_fingerprint_strict, fingerprint_sensitivity, controlled_authority_identities, block_rule_governance_fail_closed, tier_signal_v5_only, capability_proof_behavioral, hardcode_guard_v6_sound, no_tautology_proof. SSOT gates RED (2, routed 2.6B): public_execute_blocking (PUBLIC EXECUTE open on writer/builder), directus_dml_blocking (Directus owner DML open on control tables). APPLY gates (0/4, all RED): exact_plan_bound_signoff_present (0 bindings), tier_permits_apply (0 tiers apply_allowed), owner_execute_permit_valid (0 permits), scale_capability_satisfied (behavioral scale NOT_SAFE).

Readiness is consumed by the writer's execute branch; with all 6 red gates it fail-closes. Block is REAL and the completed automated contract (unlike FIX4) is wired to behavioral/structural evidence. Perf: readiness evaluates ~3.5s (MATERIALIZED edge closure + node-dedup).