Why behavior outlives implementations
Production Is a Compiler Input - The Phoenix Architecture
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
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.
Code Was Never the Asset - The Phoenix Architecture
Why AI makes the hidden economics of software unavoidable
chadfowler.com/phoenix
Reference implementation for the Phoenix Architecture. Work in progress.
The Conversation Is the Commit - The Phoenix Architecture
Compaction Is a Financial Strategy - The Phoenix Architecture
Why smaller codebases win in the AI era
Inngest - Durable Execution for Workflows & AI
Build reliable background jobs, workflows, and AI agents without extra infrastructure. Automatic retries, flow control, and step-level observability.
How Antithesis Turned exe into a Sandbox for Agentic Software Tests - exe.dev blog
Carl Sverre spends a lot of time thinking about how to give AI agents the right amount of power. Give them too little, and they can’t do real work. Give them too much, and they might blow up your tech stack. As a software engineer at Antithesis, an autonomous software testing platform, that question is core to how Sverre thinks about designing tools in the era of advanced AI.
Sprites - Stateful sandboxes
Persistent, hardware-isolated execution environments for arbitrary code. Run AI agents, untrusted code, and more in secure sandbox environments with checkpoint & restore.
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?
Environments in Managed Agents | Gemini API | Google AI for Developers
Learn about persistent execution environments for managed agents in the Gemini API, including pre-installed software, snapshots, and configuration options.
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,…
UI Is a Conservation Layer - The Phoenix Architecture
Why the user interface is the last to become regenerative