Book-Reader-Assist/library/Spec Driven Development/Chapter-03-Trilogy-map-what-lives-in-each-volume/Chapter-03-chapter-notes.md

Spec Driven Development — Chapter 03: 0b - Trilogy map: what lives in each volume

• Date Created: 2026-10-01
• Status: Complete
• Reading Span: PDF pages 20–22

---

1. Pre-Reading Briefing

• Core Question: How does Ködel divide the work of building software with AI across his three books?
• Key Points to Watch For:
  • Identify the distinct question assigned to each volume.
  • Track the order in which information moves from an idea toward an AI-assisted implementation.
  • Notice how he relates this book to FOCUS Architecture and Context Engineering, which you have also started.
  • Check his claim about whether the other volumes are required to use this one.
• Context & Thread from Prior Chapters: Chapter 2 argued that a clear target helps people direct and assess AI-generated code. This short orientation section positions that target alongside code organization and the information supplied to a model.

---

2. Reading Review & Reflections

• Prompt Questions:
  1. What question does each of the three books answer? Explain the difference in your own words.
  2. Imagine adding a feature to a small app. How would the three concerns fit together from your intended behavior to the information an AI receives?
  3. Ködel says each volume stands alone. What does he promise to do when he refers to another volume, and how would you tell whether he keeps that promise?
• User Key Takeaways:
  1. “SDD- What and Why , FOCUS - WHere boundry and address, COntext - What the agent sees , selection and cost”
  2. “What,Where, and what the AI agent needs to know and see”
  3. “Is anything he says true in my eperience and try out some of the things he suggests”
• Scaffolding & Feedback: The reader accurately recalled the three questions and their order. More precisely, SDD defines verifiable intended behavior, FOCUS locates rules in code and directs dependencies inward, and Context Engineering selects what reaches the model in a single call at a cost. The second answer captures the sequence; a concrete feature example could show how the specification and relevant code reach the agent. The third answer proposes a valuable test of the method's practical claims, but the question asked about the narrower promise that this volume stands alone. Ködel says a reference to another volume should include its name, link, and the needed point summarized in this book, without requiring the reader to open the other book. Follow-up active-recall prompt: When this volume cites FOCUS or Context Engineering, what should appear right there so you can keep reading without opening it?
• Follow-Up Response: “a small explination of the concept it is refering to”
• Follow-Up Feedback: Correct. The referenced idea should be explained where it appears, enough for the reader to continue without opening another volume. Ködel also says he will give the other book's name and link.

---

3. Chapter Synthesis

• Core Thesis: Ködel presents specification, architecture, and AI context as three connected concerns—what and why to build, where rules belong, and what information the model sees—while promising that this volume remains usable on its own.
• Key Concepts / Mental Models:
  • Spec Driven Development (what and why): Turn an intention into a verifiable target for human or AI work; use it to check whether the result meets the intended behavior.
  • FOCUS Architecture (where): Decide where each rule belongs in code and keep dependencies pointing inward; use it after the target is clear.
  • Context Engineering (what the agent sees): Select and deliver relevant information to the model for a particular call while considering cost.
  • Stand-alone volume: A cross-reference should provide the needed idea in place, with a name and link, so another book is optional for understanding the current passage.
• Notable Arguments & Evidence: The chapter gives a conceptual sequence: a specification defines the work, architecture locates it, and context carries the relevant information into the model's window. Ködel states that no volume is a prerequisite for the others. This is an organizing map and a promise about later chapters, not an empirical comparison of the three approaches; the stand-alone claim can be checked as cross-references appear.
• Updates to Prior Understanding: Chapter 2 argued that a specification gives AI-generated work a target. Chapter 3 places that target before decisions about code location and before selecting the information an agent receives. It also makes the connection to FOCUS Architecture and Context Engineering explicit.
• Weekly Action Item: For one small feature, write three short lines: the intended behavior and how to verify it; where its rule belongs in the code; and which specification and code excerpts an AI agent would need for one task.