The architecture of a regenerative system is defined entirely by what you can't delete.
Regenerative Software - The Phoenix Architecture
Compile to Architecture - The Phoenix Architecture
For a long time we’ve treated frameworks as the target of software development. But if systems are meant to be regenerated and replaced safely, the real compilation target has to be the architecture itself.
The Regenerative Grain - The Phoenix Architecture
In 2014 I gave a talk called Tiny (keep things small enough to understand) In 2026, small means something different. Small means safe to delete. New in the Phoenix Architecture series: The Regenerative GrainI
The Implementation Remembers · The Phoenix Architecture
Every mature system is carrying around lessons that were never written down. They’re encoded as validations, retries, timeouts, workflows, and exceptions. The implementation remembers. The organization forgets
UI Is a Conservation Layer - The Phoenix Architecture
Why the user interface is the last to become regenerative
chadfowler.com/phoenix
Reference implementation for the Phoenix Architecture. Work in progress.
The Conversation Is the Commit - The Phoenix Architecture
The Specification Is Not a Document - The Phoenix Architecture
Imagine joining a software project a few years from now. It is a large, mature system. It has thousands of business rules, years of operational experience,…
Production Is a Compiler Input - The Phoenix Architecture
Code Was Never the Asset - The Phoenix Architecture
Why AI makes the hidden economics of software unavoidable
When Does a Specification Become a Program? - The Phoenix Architecture
A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one?
When Does a Specification Become a Program? - The Phoenix Architecture
A spec can contain prose, tests, schemas, formal models, even executable code. The useful boundary is not the syntax but, rather, what survives: if you throw the implementation away, what has to remain so you can build the next one?
Relocating Rigor - The Phoenix Architecture
The Discipline That Looks Like Recklessness
Erase your darlings: immutable infrastructure for mutable systems - Graham Christensen
Over time, a system collects state on its root partition. This state lives in assorted directories like /etc and /var, and represents every under-documented or out-of-order step in bringing up the services.
Pace Layers and AI Integration - The Phoenix Architecture
Evaluations Are the Real Codebase - The Phoenix Architecture
Why behavior outlives implementations