The Software Phase Transition
The Software Phase Transition is a framework by Richard Ewing describing the shift from Solid (traditional roadmaps) through Liquid (adaptive pods) to Gas (autonomous AI creation) as software writing costs approach zero.
“Stop managing output. Start managing capital and uncertainty.”
In the pre-AI era, product managers spent most of their time allocating scarce engineering bandwidth and managing backlog velocity. As generative AI drives code generation costs toward zero, developer capacity is no longer the main constraint. Without economic governance, unbounded feature creation leads to exponential organizational complexity, coordination tax, and margin collapse.
Solid-Liquid-Gas Software Creation Matrix
Multi-Hop Causal Traversal Engine
Explore how concepts dynamically feed into each other across 1-hop, 2-hop, and 3-hop transitive relationships. Click any node to navigate the causal highway.
The Software Phase Transition
The Software Phase Transition is a framework by Richard Ewing describing the shift from Solid (traditional roadmaps) through Liquid (adaptive pods) to Gas (autonomous AI creation) as software writing costs approach zero.
Direct Relationships (10)
Transitive Neighbors (Connected via Hop 1)
Extended Causal Ripple Effects
The Software Creation Phase Transition
Organizational Complexity vs. Cost to Write Software (Solid → Liquid → Gas)
The Inflection Point: "We Are Here"
The Phase Transition from Code Scarcity to Code Abundance
The current industry inflection point where traditional PM frameworks break down. As developer capacity ceases to be the constraint, product leaders must stop managing output and start managing capital and uncertainty.
Bridging agile backlog workflows with AI-assisted generation while restructuring governance around product economics.
Executive cognitive models locked in legacy output metrics while engineers deploy AI-generated code.
Measuring sprint velocity rather than capital efficiency; allowing unchecked token COGS to erode SaaS margins.
Deploy the Product Economist playbook: audit R&D capital allocation, measure Product Debt Index (PDI), and gate AI feature margins.
Reverse Citations: Implemented & Audited Across Platform
Richard Ewing’s Research Thesis
When the marginal cost of writing software approaches zero, engineering velocity is no longer the bottleneck. The competitive differentiator is risk reduction, system architecture efficiency, and unit margin preservation.
Why This Specification Exists
Product teams use legacy sprint backlog and velocity frameworks in an era where AI agents spin up features in hours, causing organizational chaos and margin collapse.
Measuring sprint velocity, story points, and feature volume.
No model connecting the marginal cost of code generation to organizational complexity and governance requirements.
Created the Solid-Liquid-Gas Phase Transition model to guide product leaders in shifting from output management to capital and uncertainty management.
What Changes If You Believe This?
Shift focus from raw code authoring to system architecture efficiency and verification gates.
Model software features as variable capital investments with strict unit margin floors.
Transition from managing feature backlog output to evaluating product economics and reducing uncertainty.
Deploy deterministic runtime boundaries to govern autonomous agent creation loops.
Specification Maturity & Ecosystem Spread
Recommended Action by Role
Stop prioritizing developer capacity; start managing risk reduction, system architecture efficiency, and unit margin preservation.
Product Debt Index (PDI)
Quantify the carrying cost and valuation drag of unmanaged software feature accumulation.
Latest Publications & Research Activity
The Engineering Bottleneck Illusion: What Copilot Adoption Taught Us
Cursor vs Google Antigravity for Production AI Building
Most Companies Shouldn’t Be Using Autonomous Coding Agents Yet
Frequently Asked Questions
Q:What is the Software Phase Transition?
The structural shift in software organizations from Solid (traditional roadmaps and PRDs) to Liquid (adaptive teams) to Gas (autonomous AI-driven creation) as code costs fall to zero.
Q:Why do traditional PM frameworks break down when code cost is zero?
Traditional PM was designed to allocate scarce developer bandwidth. When code generation is free, managing backlog velocity creates feature bloat and margin erosion instead of value.
Canonical Specification Origin
When the marginal cost of writing software approaches zero, engineering velocity is no longer the bottleneck. The competitive differentiator is risk reduction, system architecture efficiency, and unit margin preservation.
Corpus Interconnections
Richard Ewing artifacts developed around this canonical framework, including publications, execution tools, and diagnostic models.
External Adoption & Peer Citations
Documented instances where independent researchers, engineering teams, and publications have cited, implemented, or referenced this concept outside Richard Ewing’s ecosystem.
External Evidence: No independently verified references recorded yet.
This concept is part of Richard Ewing’s original baseline canon. External citations and implementations are added only upon rigorous empirical verification.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
| Evidence Item | Publisher | Evidence Type | Strength | Role | Action |
|---|---|---|---|---|---|
| The AI Economist: Leading Product Strategy When Build Costs Approach Zero | Executive Publication | ★★★★★ | Extends | Inspect ↗ | |
| When the Cost of Writing Software Approaches Zero, Traditional PM Frameworks Break Down | Executive Publication | ★★★★★ | Origin | Inspect ↗ |
Translating The Software Phase Transition into Execution
When AI collapses the cost of code generation toward zero, engineering backlog velocity ceases to be the constraint, shifting the bottleneck to managing uncertainty and unit margins. Impact: Unbounded feature bloat and coordination taxes cause product margin collapse.
R&D Capital Allocation & Product Economics Advisory
Restructure your product organization from solid backlogs into adaptive pods governed by unit economics.
Measure R&D Velocity Drag via PDI
Quantify organizational carrying costs and debt drag across phase transition pods with the Product Debt Index.
Note: Research specs and evidence ledgers remain independent and factual. Downstream pathways provide verified implementation channels for teams managing this operational problem.
Recommended Citation
Ewing, R. (2026). "The Software Phase Transition." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/software-phase-transition
@article{ewing_software_phase_transition,
author = {Ewing, Richard},
title = {The Software Phase Transition},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/software-phase-transition}
}