The sandbox has never matched production. Not yours, not anyone's. A configuration variable set differently. A database seed that skips the legacy record formats real users actually have. An upstream service that deployed a new response schema last Thursday and nobody updated the simulation. These are not edge cases - they show up in every environment, on every team, at every scale. The gap is structural. It comes with the territory. What changes when you accept that is where you put the maintenance work.
Drift accumulates because production and the sandbox change on different schedules, with different triggers, and nobody coordinates the two deliberately enough.
Production evolves constantly. Application deployments, infrastructure updates, upstream service API changes, database schema migrations, third-party integration updates - each of these moves production forward in some dimension. The sandbox catches some of these changes when someone explicitly updates it.…