As AI systems become capable of writing, modifying, and operating software autonomously, we are entering an era where code is abundant and change is continuous. But if software increasingly builds itself, what exactly are we architecting?
This talk explores how the rise of autonomous development reshapes what architecture means. Traditional patterns - from microservices to API contracts - were designed for human teams working at human speed. When AI agents can generate services, refactor systems, and negotiate interfaces at machine pace, those assumptions no longer hold.
We’ll examine three fundamental shifts. First, architectures must become machine-comprehensible - not just documented for humans, but structured so agents can reason about change. Second, we move from designing systems to designing guardrails: encoding intent, cost boundaries, and risk tolerances that constrain autonomous behaviour. Third, human understanding no longer scales by default; when systems evolve at machine pace, comprehension and oversight must be designed deliberately.
These shifts redefine what it means to shape software. Translating strategy into machine-readable constraints, maintaining clarity amid constant change, and governing systems where authorship is shared between humans and AI become core concerns.
The future isn’t codeless - it’s architecture-first. When change is automated, the stability, trust, and intent of our systems depend on how deliberately we design the environments in which they evolve.
Matthew Clark is Head of Architecture for the BBC’s online products. Over 15 years at the BBC, he has worked on hundreds of projects - from delivering coverage of Olympic Games around the world to helping get BBC iPlayer running on the International Space Station. His focus is technical strategy: how emerging technologies can be applied pragmatically to solve real problems, move faster, and create...