How to Read This Book

This reference section of the book contains a summary of its six central claims, a diagram connecting them, and a glossary for reference.

First time here? Read What This Book Argues, then the Preface, and continue into Chapter 1.

Looking for a refresher? Use What This Book Argues for the six central claims and their relationships, and the Glossary for definitions.

The book asks how we can safely grant autonomy to commodity intelligence. Chapter 1 frames the engineering problem. Chapters 2–5 develop MAGE through software engineering, explaining its mechanisms and examining the evidence. Chapter 6 develops the theory, Chapter 7 considers its broader implications, and the Conclusion asks what engineers remain responsible for when they delegate the work. Figure 0.1-1 traces the progression.

The book's argument in three movements — the engineering question, the nested software-engineering case, and the engineering argument it substantiates, from the Preface's question to the Conclusion's answer A single descent through the book's argument, in three movements. The Preface poses the opening question: how do we safely grant autonomy to commodity intelligence? It leads to Chapter 1, The New Engineering Problem — changed economics. A subtly shaded region then nests the software-engineering case — the chapters that develop the mechanisms and supply the evidence. Inside it: Chapter 2, Modeling — make knowledge and intent explicit. Then Chapter 3, Alignment — enforce selected obligations. Then Chapter 4, MAGE in Motion — the mechanisms put in motion on a worked problem: model, align, work, convert. Then Chapter 5, Agentic Software Factories — the production system that supplies the evidence: a deep case, industrial variation, and what the factories show. The descent leaves the case region at Chapter 6, The Theory — the abstraction from those factories: dynamics, economics, predictions, and scope conditions. Then Chapter 7, The Profession — how software work reorganizes, agentic engineering beyond software, and the responsibility that remains the engineer's. The descent ends at the Conclusion, which returns to the Preface's question and asks its converse: what cannot be delegated? Responsibility. question → worked case → theory → implications → answer Preface “How do we safely grant autonomy to commodity intelligence?” Chapter 1 · The New Engineering Problem changed economics THE SOFTWARE ENGINEERING CASE mechanisms · practice · evidence Chapter 2 · Modeling make knowledge + intent explicit Chapter 3 · Alignment enforce selected obligations Chapter 4 · MAGE in Motion model · align · work · convert Chapter 5 · Agentic Software Factories deep case · industrial variation · production systems abstract from the factories Chapter 6 · The Theory dynamics · economics · predictions · scope Chapter 7 · The Profession software work · broader engineering · responsibility Conclusion returns to the question, and asks its converse: “What cannot be delegated?” — RESPONSIBILITY
Figure 0.1-1. The book’s argument. The software-engineering case leads to theory, broader implications, and responsibility.

Readers can also take shorter routes:

  • Try it Monday: Chapter 1 → Chapter 4 → Appendix B.
  • Adopt it in an organization: Chapter 1 → §5.4 → Appendix B.
  • The theory: Preface → Chapter 1 → Chapter 6.
  • Coming from another discipline? Preface → Chapter 1 → §7.3.
© James C. Davis, 2026–present