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 Phoenix Primitives - The Phoenix Architecture
The architecture of a regenerative system is defined entirely by what you can't delete.
Regenerative Software - The Phoenix Architecture
The Conversation Is the Commit - The Phoenix Architecture
UI Is a Conservation Layer - The Phoenix Architecture
Why the user interface is the last to become regenerative
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
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.
chadfowler.com/phoenix
Reference implementation for the Phoenix Architecture. Work in progress.
Compaction Is a Financial Strategy - The Phoenix Architecture
Why smaller codebases win in the AI era
Relocating Rigor - The Phoenix Architecture
The Discipline That Looks Like Recklessness
Read · oblachek's “Grain” review | at-store
4/5 — Open to read the full review on at-store.
The Spec Can Come Later - The Phoenix Architecture
When I say things like "delete the code, keep the spec," many people seem to interpret that as a rule: write the specification first, and only then are you a…
The Spec Can Come Later - The Phoenix Architecture
When I say things like "delete the code, keep the spec," many people seem to interpret that as a rule: write the specification first, and only then are you a…
Production Is a Compiler Input - The Phoenix Architecture
Caring for the Chips: Repair and Reuse as Permacomputing – Michelle Kaczmarek
