Module 12 Summary
What this module established
A bar must name the set, the judge, a zero-tolerance metric and the operational bounds - one made entirely of rates permits every failure at some frequency. Evaluate each dimension against its own bar and let the weakest decide.
Carry forward
- Report latency at p50, p95 and p99, and state which rates are by design. A refusal rate matching your eval set is healthy.
- Add a tested column to the failure-mode table. A page of unverified mitigations reads as better coverage than it is.
- The report's output is a decision and a set of gates. A reliability report that never blocks a release is a report nobody is running.
Before moving on
You have finished when your report reaches a verdict against bars set beforehand, and proposes gates specific enough for someone else to run without asking you a question.
