With the current state of coding harnesses that produce OpenAPI descriptions in incredible detail, the human aspect of the OpenAPI specification—viewing and editing— is no longer needed. The protocol should go all the way to tooling.

I open a screen full of terminals, each in a different repository. Each one is one of my AI assistants, ready to accept tasks. I usually have two or three running at the same time, thinking, planning and acting. It looks like a scene from a hacker film. It is not — the repos are almost entirely Markdown. Three layers, and only one is disposableEvery AI assistant I run is set up the same way.

A change is breaking if a client that worked yesterday has to change its code, its configuration, or its infrastructure to keep working today. That includes changes that keep every client running while quietly giving it wrong data — those are still breaking, only harder to notice. Most of the list below follows from one rule. On the request side, anything that narrows what the API accepts is breaking, because traffic that was valid yesterday must stay valid.