Technical Documentation

How We Build Software With AI

38 papers documenting the Compounding Execution Method — extracted from real builds, not theory.

38
Papers
4
Paper Types
28
Techniques
10
Systems Validated
Core Concepts 3 Build Patterns 5 Recovery Guides 2 The Techniques 28 Setting Direction 4 Execution Rhythm 5 Speed & Quality 4 Course Correction 7 Knowledge & Accuracy 4 How We Structure Work 4
38
Papers
4
Paper Types
28
Techniques
10
Systems Validated

Start with the Core Concepts — they explain why old methods fail when AI enters the picture. Then explore the 28 techniques, organized by what problem they solve. Build Patterns show how everything combines in real projects. Recovery Guides are for when things break. You don't need to read all 38. Start with the foundations, then follow what's relevant to your work.

1 Core Concepts 3 2 Build Patterns 5 3 Recovery Guides 2 4 The Techniques 28

Build Patterns

5

Techniques don't run in isolation. These papers show how they combine under real production pressure — parallel builds, time compression, knowledge capture — patterns extracted from shipping 10 systems in 116 days.

Start with: Build as Validation
A1 Build Pattern Build as Validation Build-as-Validation: The Inversion of Lean Startup When Building Cost Approaches Zero When building is cheaper than asking, the product becomes the experiment. Read paper
A2 Build Pattern Parallel MVP Simultaneous Validation Across Engineering, Product, and Marketing How I stopped sequencing build, test, and sell -- and started shipping all three in the same week. Read paper
A3 Build Pattern Time Compression Accelerating Cycle Velocity Through Foundation Depth How Foundation depth compressed my MVP delivery from 43 days to 4 days across ten production systems — not through simpler projects, but through a system that compounds. Read paper
A4 Build Pattern Routing Bidirectional Patch System for Sustained Operator Progress How upward patches to experts and downward patches to delegates kept me executing at my optimal capability level -- never blocked by my own limitations, never slowed by work beneath my level. Read paper
A8 Build Pattern Knowledge Formalization Extracting Methodology From Execution Data Through CEM How I turned an unnamed personal methodology into a published, DOI-stamped body of work in 12 days — using the same mechanisms that built the software portfolio. Read paper

The Techniques

28

28 techniques extracted from building 10 production systems. Each sub-section below solves a different category of problem — from setting direction to recovering from mistakes.

Start with: Vision