AI-First Theory
The scientific foundation. Two axioms about AI systems and human tacit knowledge; six theorems that follow from them. Together they describe what happens to the software development lifecycle when AI systems can read, write, and verify code at production grade.
Engineering needs a ground truth, not a framework
Most discussions of AI in software development are tactical: which tool, which prompt pattern, which IDE integration. The upstream question: what, formally, is changing?
AI-First Theory answers in terms suitable for reasoning, falsification, and extension. Not a framework. Not a manifesto. A compact set of propositions, stated precisely enough to disagree with, find edge cases in, or extend.
Theory → Manifesto → RACE Programming. Each layer more prescriptive. Each depends on the one above being sound.
Two axioms and the core skill
The foundation everything rests on, for engineers and knowledge workers alike. Two claims taken as premises, and the one skill that follows immediately from them.
Five consequences, two audiences
With the base in place (the two axioms and delegation), the remaining five theorems split by who they are for: three for software engineers, two for knowledge work at large. Read each set together, or any theorem on its own page.
For software engineers
The empirical core: where AI leverage lands, the team structure that follows, and the cost paradox. This is what grounds RACE Programming's design.
- Tech Leads Are 10x EngineersFull SDLC experience + delegation skills + AI tools = a 10x one-person orchestra. A mathematical certainty given the skill set; the only variable is time to adoption.
- One Small Pizza Team Is a New Two Pizza TeamEngineers without delegation accelerate ~3x, not 10x. Coding speeds up 20x but is only ~30% of delivery. A 3-person micro-team matches a 9-person Scrum team.
- The Paradox of Enterprise Development CostAI raises capacity, but demand (vibe-coders, automation appetite) outpaces it. Efficiency rises; the cost of enterprise development paradoxically does not fall. It keeps growing.
Read the Engineering Theorems together →
For knowledge work
The broader thesis: how the labor market stratifies into a new aristocracy, and why the same fracture spreads to every white-collar field.
- AI Creates a New Aristocracy, Not EqualityAI filters rather than democratizes: 4% elite (10x), 16% adapters (3x micro-teams), 80% pure coders displaced. The pre-AI delegation advantage compounds.
- The Fractal Stratification of Knowledge WorkSoftware is Patient Zero. The same three-tier fracture (AI Aristocracy, Synthetic Micro-Teams, Displaced Layer) scales to every white-collar industry.
What this theory is not
Not a claim about AGI, consciousness, or the singularity. Narrow scope: current-generation AI systems (LLMs with tool use and code execution) × structure of software engineering work. Intended to remain valid across model generations, operating above any specific model.
Not a claim that engineers disappear, but a claim about which engineers thrive. Pure code-writing is displaced; engineers who master delegation and own a domain compound their advantage. The theory describes how the market stratifies, not a target to aim for.
Reading order
Fast path: the base (axioms + delegation) → T2 (Tech Leads Are 10x Engineers) → T3 (One Small Pizza Team), both on the Engineering Theorems page. Sufficient to understand why RACE Programming looks different from Scrum. Complete picture: read all six in order, since later theorems build on earlier ones.