05 - Hardcode and Metadata-Driven Audit

Verdict

The planner removed the fixed 39-collection UNION, but the control plane still contains dangerous direct hardcode and hardcode disguised as metadata.

Dangerous

• Fixed five-collection Tier1 list repeated in views, snapshot refresh, guards, rehearsal, and checks.
• Literal independent_reaudit_signed_off=false; code edit required and writer ignores it.
• Tier classification derived from fixed list and flawed parity formula; not governed/writer-enforced.
• Permit template includes literal Tier1/Tier2.
• legacy_id_single_colon resolver emits collection::id while realtime emits collection:id.
• inferred_from_existing_trigger metadata is not continuously reconciled to live trigger.
• existing_births=matched current source rows violates birth conservation.

Conditional/Acceptable

Literal 137/5/8/42/129/fixed MD5 are temporary drift pins only if never authority gates. Planner discovery from governed collection_registry and dynamic quoted identifiers are metadata-driven only when trigger/identity parity is enforced.

False-Pass Guards

Fresh snapshot means count>0, with no TTL/checksum. Resume guard proves a column exists, not behavior. Collision guard ignores expected_delta=0 despite 103 live collisions.