2.7KB
Spec Driven Development — Chapter-03: 0b - Trilogy map: what lives in each volume
- Source: /library/Spec Driven Development/source-file.pdf
- PDF pages: 20–22
- Pages without text: none
0b - Trilogy map: what lives in each volume This is the first book in a trilogy and you do not need the other two to finish it. Each volume stands on its own. This chapter exists for a practical reason: further along, the text will cite its siblings in a few passages, and it is better for you to know beforehand what lives in each one than to find out in the middle of an argument. The three answer different questions about the same work. This book answers what and why: how to turn a vague intention into a verifiable specification, so that the work, yours or an AI's, has a target to be checked against. It comes first because without it the other two have nothing to organize. FOCUS Architecture (2026, https://books.kodel.com.br/en/books/focus/) answers where: where each rule lives and why dependencies point inward. The acronym opens up into Feature-Oriented, Clean, Unidirectional and Scalable, four adjectives for code organized by feature, with clean layers, with dependencies pointing in a single direction and with room to grow. It is the answer for when the specification is ready and you have to decide which file the thing it asks for will land in. Context Engineering (2026, https://books.kodel.com.br/en/books/context-engineering/) answers what the agent sees right now, in the window of this one
call, and at what cost. A model does not know your project; it knows whatever fit into the conversation at that moment. Choosing what goes in there, delivering it at the right time and paying as little as possible for it is a craft of its own, and it is the subject of the third volume. The order of the arrows is the order information travels in, and it works as a route for anyone who wants all three: the specification says what to do, the architecture says where what it asks for happens, and context carries both, in the right dose, into the model's window. None of that is binding. Whoever reads only this volume walks away with a complete method in hand. None of the three is a prerequisite for the others, and this book was written to hold up that promise in practice. From here on, when a sibling volume shows up, it shows up as a cross-
reference: the name of the book, the link and whatever you need to know summarized right there, in the sentence itself. You will never have to interrupt your reading, open another book and come back. If some passage further along only closes with outside reading, that is a flaw of mine, not a design choice.