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

208Readers

23Posts

1mo agoLast active

Add to list

The Implementation Remembers

Jun 14, 2026

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

Production Is a Compiler Input

Apr 20, 2026

#ai#software

The Phoenix Primitives

Apr 13, 2026

The architecture of a regenerative system is defined entirely by what you can't delete.

#coding#ai

The Generative Stack

Apr 7, 2026

Trying to find the best tool or platform for generative software in 2026 is a mistake that could haunt you for decades

#ai#coding

The Conversation Is the Commit

Mar 26, 2026

#ai#software

Compile to Architecture

Mar 6, 2026

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.

#ai#coding

The Regenerative Grain

Feb 19, 2026

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 Industrialization of Regenerative Software

UI Is a Conservation Layer

Jan 21, 2026

Why the user interface is the last to become regenerative

#ui#ux

Provenance Is the New Version Control

Jan 13, 2026

#ai#code

n=1 Is a Design Constrain (Not a Staffing Model)

Jan 7, 2026

Single-developer capability isn’t a productivity story. It’s the test that tells you whether your architecture is worth keeping.

#ai#productivity