03 — Tier Registry SSOT (SUPERTRACK C)

Tiering is now explainable and data-driven, and — critically — every tier has apply_allowed = false in Stage 2.6A. The writer/readiness path can read tier gates from the registry in a later layer.

Objects

• Table qt001_tier_registry — columns: tier_code, tier_rank, eligibility_rule, validation_source, allowed_action, required_review, apply_allowed, reason, scale_risk, parity_requirement, updated_at.
• Views v_qt001_tier_registry_current, v_qt001_tier_gate_status (joins live plan counts per tier), v_qt001_tier_no_go_guard.

Encoded tiers

tier_code	apply_allowed	allowed_action	required_review	reason
TIER1_CODEX_VALIDATED	false	PLAN_ONLY	fresh independent re-audit (SAFE on current plan checksum) + owner execute permit	data valid but runtime/permit/authority/scale NOT_SAFE per Codex
TIER2_METADATA_CONSISTENT_UNVALIDATED	false	PLAN_ONLY	independent validation of classified identity vs realtime TG_ARGV, then re-audit + permit	consistent metadata but identity not independently validated
TIER3_PARITY_DIVERGENT_RECLASSIFY	false	RECLASSIFY_ONLY	TG_ARGV re-mirror + conserved-history/identity-mismatch separation, then re-audit	backfill today would DUPLICATE; writer fail-closes
TIER_INELIGIBLE	false	NONE	identity classification / owner decision	not an apply candidate (no delta / unresolvable / ineligible)

Eligibility rules (as data, not code)

TIER1 = eligible AND expected_delta>0 AND parity CONSISTENT AND has a DATA_VALID review row. TIER2 = same but no review row. TIER3 = eligible AND expected_delta>0 AND parity DIVERGENT. TIER_INELIGIBLE = otherwise. These mirror the plan-registry derivation so the registries agree.

No-go guard

v_qt001_tier_no_go_guard.pass = true: tiers_defined 4, tiers_apply_allowed 0. The writer is blocked by the tier gate because no tier permits apply. A later layer flips a tier's apply_allowed only under the governed conditions in required_review.

Why this supersedes HC-06

The permit template's literal TIER1/TIER2 strings are replaced as SSOT by this registry; permit issuance in the next layer must bind tier_code from qt001_tier_registry rather than embedding literals.