Appendix A. Bridges to the First Volume

The applied volume builds on the material from the first volume. This appendix gathers all the bridges in one place: which parts of the first volume are considered prerequisites, how our SDD dialect relates to Spec Kit and Kiro, and how the production scenarios of the second volume grow out of the educational AgentClinic project.

If anything from the list is unfamiliar, first go through the corresponding part of the first volume; otherwise many chapters of the second volume will seem like a pile of terms.

Before chapter 1, read part 0. It translates the basic AgentClinic into an educational production model and fixes the minimum path: which artifacts are filled in manually, which examples run locally, and which blocks belong only to the full deployment track.

The minimum without which the second volume cannot be read

SDD Dialects: Spec Kit, Kiro, the Author's Textbook Dialect

The applied volume uses the same author's dialect as the first volume. A detailed comparison with GitHub Spec Kit and AWS Kiro is given in Appendix A of the first volume: a table of artifact correspondence, recommendations for transferring the process, and limitations of each format.

If the team already works in Spec Kit or Kiro, read the chapters of the second volume while mentally renaming requirements.md → /speckit.specify, plan.md → /speckit.plan + /speckit.tasks, validation.md → /speckit.analyze + checklists. The chapters are not rigidly tied to the format: their ideas transfer between dialects without loss of meaning.

AgentClinic Domain Map

The production scenarios of the second volume are mentally deployed on the educational AgentClinic project from the first volume. A full description of the domain entities — patient agents, ailments, therapies, appointments, reviews, feedback — is collected in Appendix B of the first volume.

The second volume does not require the result of the first volume to already work in real production infrastructure. All external systems in the chapters are educational sources of events and constraints. They are needed to show how the same SDD cycle behaves under the risk of rollback, escalation, metrics, and model budgets.

When production entities appear in the second volume (appointments-api, node_not_ready, appointment_latency, appointment_latency_spike, high_memory_usage, autoscale_200pct, cdn_error_budget_burn, rate_limit_breach), they are tied to AgentClinic as follows. For the capstone path, use high_memory_usage as the main case; the other rows help you understand the local runnable examples and do not require a separate evidence bundle.

The README of the applied volume provides a short reading map and a link to this appendix. The full domain table lives here so that when reading any chapter of the second volume, you can quickly recall which educational code corresponds to the production symptom.

What the Second Volume Added on Top

The table above is the bridge that turns an abstract production scenario into a continuation of the educational project. In some chapters of the second volume (for example, in part 12 — production SDD antipatterns), references to the first volume are also placed in a separate block at the bottom; in the other chapters, they are woven into the text at the point of discussion.