06 - Tier Validation

Tier1 - 5 Collections / 137

Data technically valid now: dot_domain_rules 67, apr_approvals 42, normative_relations 18, apr_action_types 6, field_type_equivalences 4. Trigger parity/key uniqueness/collision evidence passes. Tier1 is not safe to apply because runtime/permit/authority/scale controls fail.

Tier2 - 2 Collections / 137

measurement_registry 132 and law_catalog 5 have consistent technical identities, unique keys, zero collision. No governed independent-validation artifact; tier is computed and writer does not block it. Keep blocked.

Tier3 - 6 Collections / 505

law_dot_enforcement 272, law_jurisdiction 43, governance_relations 8 expose wrong double-colon legacy resolver versus realtime single-colon. table_registry 20 and workflows 2 each have two birth triggers with different identity behavior. approval_requests 160 has 11 conserved historical births without current source rows; current parity formula misclassifies these as divergence.

Twenty-one snapshot collections show nonzero divergence, including legitimate historical births. Current parity invariant cannot distinguish identity mismatch from conserved history.