Regenerative Software [Book]
The assumptions underneath modern software development have quietly broken. Version control assumes humans make changes incrementally. Code review assumes a human authored the code. Testing assumes you can reason about what changed. When AI generates, modifies, and regenerates code autonomously, these abstractions don't just strain—they stop making sense.
Regenerative Software by Chad Fowler introduces a new model built for this reality. Rather than maintaining codebases indefinitely, this new model treats code as a derived artifact. With practical frameworks for provenance tracking, selective regeneration, and agent-driven architecture, this is the architectural reference the industry has been waiting for since AI became the primary author of code.
- Design systems where code is a derived artifact, not a permanent accumulation of decisions
- Implement provenance tracking that replaces version control as the source of truth
- Build architectures where AI agents operate as first-class developers
- Evaluate trade-offs between regeneration and stability across production systems
- Introduce regenerative principles incrementally into existing codebases
Post | LinkedIn by Chad Fowler | LinkedIn
The Phoenix Architecture
Generative AI coding demands what we've always known: modularity, clear boundaries, disposable components. Principles that scaled human teams are now table stakes. Here, we make the implicit explicit
This collection of essays by Chad Fowler outlines The Phoenix Architecture, a blueprint for building software systems designed to thrive alongside AI coding tools.
Key Themes & Takeaways
Code Is Disposable, Architecture Is Forever: As AI makes writing code trivial, individual implementations become temporary. The true assets of a system are its architectural boundaries, specifications, and test evaluations—not the generated code itself.
The Deletion Test & Disposable Components: High-quality AI architecture requires extreme modularity and clear boundaries. The core metric for system health is how safely and easily a component can be deleted and regenerated from scratch.
Specifications Outlive Code: A specification (combining schemas, tests, prose, and behavior models) is what survives when an implementation is discarded. Evaluative tests act as the true "codebase" by defining acceptable behavior across iterations.
"Never Upgrade in Place" for Code: Treating code like immutable infrastructure—replacing components rather than modifying them in place—minimizes technical debt and prevents hidden complexity from accumulating.
Shift in Developer Rigor: Rigor moves upstream from writing syntax to refining specifications, system design, and continuous validation, allowing single developers ($n=1$) to operate with system-level impact.
