Part V - System cases, diagnosis, and release decisions
A release decision concerns the complete system, not one prompt, retriever, model, or tool in isolation. The evidence must show which component produced each result, which failures remain, and how the system behaves within its time, cost, and safety limits.
This Part combines task definitions, evaluation results, retrieval traces, tool steps, saved-state changes, cost and latency into system cases. The execution logs support investigating failures, choosing a sufficient design and deciding whether release requirements are met.
Chapter 12 follows evaluation, RAG, and support-agent cases through their logs and checks, then tests a small runnable subset with local stand-ins. Chapter 13 explains stage-specific logging, established standards and logging tools. Chapter 14 connects architecture choices and failure diagnosis to release requirements for quality, evidence support, tool control, infrastructure, cost and latency.