Why APIs Rot — The Compatibility Contract You Signed Without Reading
The day an API gets its first external integration, its shape stops being yours. Every field name, every status code, every undocumented quirk becomes load-bearing for code you can't see, written by teams you can't reach, deployed on schedules you don't control. API evolution is the discipline of changing a thing that thousands of strangers depend on — and it begins with understanding exactly what you promised, because most breakage comes from changes the provider genuinely believed were safe.
The real contract is operational: a change is breaking if any plausible client stops working — extending past docs into everything observable (Hyrum's Law), split across tolerant and strict readers. Rot decomposes into nameable forces: design debt, version sprawl, spec drift, zombie clients, change aversion. Opens the series.