Orientation and Reference

How to Read This Book

This front matter is reference material. You do not need to understand it before beginning the book.

First time here? Read the Preface and continue into Chapter 1. You may skip the rest of this front matter for now; it is designed to become more useful as the terminology and argument become familiar.

Returning to the book? Use What This Book Argues for the six central claims, MAGE on One Page for the relationship among the major concepts, and the Glossary for definitions.

The Preface asks one question: How do we safely grant autonomy to commodity intelligence? Chapter 1 frames the resulting engineering problem. Chapters 2–5 then develop MAGE through software engineering: they show the mechanisms in a worked domain and provide the evidence from which the broader account is drawn.

The software-engineering case proceeds at two levels of abstraction. Chapter 1 begins with the new fabricator: a capable agent that can realize software from engineering intent. Chapters 2–4 develop the representations, Alignment mechanisms, and engineering practices needed to operate that fabricator while retaining control over consequential properties. Chapter 5 then considers the production system around it. At this second level of abstraction, the fabricator becomes one component of an agentic software factory: a system that organizes production, determines which variation is acceptable, evaluates what has been produced, and changes when its controls prove inadequate. Chapter 6 develops a theory of the resulting allocation of engineering work, and Chapter 7 considers its implications for the profession.

Chapter 6 abstracts that experience into a theory; Chapter 7 asks what follows for engineering more broadly. The Conclusion returns to the opening question and asks its converse: What cannot be delegated? Figure 0.1-1 traces that argument.

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; a dotted branch runs to Appendix Part I, Practice (use and extend). Then Chapter 5, Agentic Software Factories — the production system that supplies the evidence: a deep case, industrial variation, and what the factories show; a dotted branch runs to Appendix Part II, Evidence (inspect the empirical record). 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. The dotted appendix branches are related destinations, not steps in the argument. 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 Appendix Part I · Practice use + extend Chapter 5 · Agentic Software Factories deep case · industrial variation · production systems Appendix Part II · Evidence inspect the empirical record 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 Preface and Chapter 1 establish the engineering problem. Chapters 2–5 develop and substantiate MAGE through its software-engineering case study. Chapters 6 and 7 abstract from that case to theory and broader engineering implications, and the Conclusion returns to the opening question through responsibility.

The argument and the case can also be read at different depths. Readers primarily interested in MAGE as an engineering argument can follow the Preface → Chapter 1 → Chapter 6 → Chapter 7 → Conclusion. That route gives the problem, theory, broader implications, and closing claim. Chapters 2–5 are what substantiate that argument: they develop MAGE through software engineering, show its mechanisms at engineering resolution, and provide the evidence from which the theory is drawn. Read them straight through for the full case, or return to them when you want to see where a theoretical claim came from.

Coming from another engineering discipline—or from work that may be engineering in the functional sense used here? Start with the Preface, Chapter 1, and §7.3. From there, Chapter 6 gives the theory, while Chapters 2–5 provide the software-engineering case from which it was developed. Circle back as the mechanisms become relevant to your own work.

Three shorter routes serve different purposes:

  • Do it Monday. Chapter 1 → Chapter 4 → Appendix Part I: Practice. Start with the premise, move directly to the working method, then use the practice appendices as a reference while applying it.
  • Show me the evidence. Chapter 1 → Chapter 5 → Appendix Part II: Evidence. Read the framing, examine the empirical argument, then inspect its evidentiary basis.
  • Give me the engineering argument. Preface → Chapter 1 → Chapter 6 → Chapter 7 → the Conclusion. Read the problem, the theory, where it transfers beyond software engineering, and the responsibility that closes the argument. Chapters 2–5 remain the evidentiary foundation; return to them to see where a theoretical claim came from.
  • Adopt it in an organization. Chapter 1 → §5.3 → Appendix G. Start with the changed engineering problem, see how several organizations are already restructuring agentic work, then use the adoption guide to decide where context, models, evidence, and enforcement are worth organizational investment. Chapters 2–4 provide the engineering practices; Chapter 6 provides the underlying theory.
© James C. Davis, 2026–present