When AI Agents Stop Writing Code and Start Modifying Systems

A follow-up to Designing Tech Stacks for AI-Generated Code AI agents are moving from code generation into live system intervention. That transition changes what "good architecture" means, and most current stacks are not designed for it. The previous piece was about reducing the surface area agents have to reason about when writing code. This one is about a harder question: what architectural conditions make it safe for an agent to modify the thing it's already running on? Two different problems There is a meaningful gap between an AI agent that writes code and one that maintains a running system. The first is a productivity story. The second is an architectural one, and it's the one the industry has not seriously engaged with yet. When an agent can not only write a schema migration but also apply it, validate the system's behavior afterward, and roll back autonomously if something looks wrong, the infrastructure is no longer a static target. It is a dynamic surface the agent is continu