How to Use This Book
Most readers come to this book with one urgent pressure, not with a plan to read every chapter in one sitting. Some need to restore approval discipline around AI-assisted work. Others need to repair model drift between specification, design, runtime, and evidence. Choose the path that matches the decision pressure in front of you. In every case, the book carries the primary reading experience. Use the companion repository later when you want to inspect the running example, validators, or file-level realization of a chapter claim.
Read it front to back if you are adopting the full method
Read the Preface, this guide, the Introduction, and Chapters 01 through 10 in order. This path is best when you want one method for architecture, review, orchestration, and evidence rather than a set of local fixes. It preserves the intended narrative arc from responsibility boundaries to orchestration, effects, and the full case study.
Start with the governance path if your urgent problem is authority and review
Read the Introduction, Chapter 01, Chapter 03, Chapter 09, and Chapter 10. Use this path when your immediate concern is who may approve AI-assisted work, which evidence must exist before execution, and how execution remains auditable after approval.
Start with the architecture path if your urgent problem is model integrity
Read the Introduction, Chapter 01, Chapter 02, Chapter 03, and Chapters 04 through 07. Use this path when your team already has a delivery workflow but struggles with view consistency, variation, migration, or integration boundaries across multiple system models.
Start with the delivery path if your urgent problem is orchestration
Read the Introduction, Chapter 01, Chapter 08, Chapter 09, and Chapter 10. Use this path when concurrency, tool use, effect boundaries, and acceptance evidence are the dominant operational concerns in day-to-day delivery.
Use the companion material selectively
The canonical running example remains the shortest operational proof of the book’s claims. When a chapter points to an artifact, inspect it after the prose has established the main claim. Use the companion to confirm how the argument lands in a versioned workflow with inspectable artifacts. Do not reverse the dependency. The chapter should explain the main argument on its own, and the repository should deepen inspection rather than carry the whole explanation by itself.
Use the appendices as stable references
Appendix A is the notation and diagram desk reference when you need to decode a figure quickly. Appendix B is the canonical vocabulary reference when you need a stable definition. Appendix C maps chapters to selective external sources when you want to deepen one concept without leaving the book’s structure behind. Appendix D shows how the same method transfers into adjacent domains without replacing the main running example.