5.7 The Eval-Driven Development Loop

Use eval failure analysis as product strategy input — tracing a 30% modification failure rate to a context retrieval gap, or a 20% deployment failure to a build/runtime split — so each failure category maps to a specific investment hypothesis, not a vague quality complaint.