Take a breath. Let's break this chapter down like a conversation, not a textbook, so it's easy to follow.
Let's think about it this way for a sec
An eval builds confidence. It doesn't hand you total proof. Things can still break on a new question, a new file, a new model. So don't say 'evals passed 100%, ship it to production.' It's like a restaurant tasting three dishes and then cooking for 300 guests. The honest thing to say is: 'These cards passed, but this is all we tested.' That's not embarrassing — that's maturity.
Let's connect it to everyday life
Write the coverage at the top of your pack. 'Tested: phone policy, missing due date, fortune-telling trap. Not yet tested: uniform rules, other people's grades, generic questions.' Never tell users 'the AI is always right.' And if a card fails, don't ship the product right away — fix the card first, then write your notes.
Let's try it together, hands-on
Coverage
Tested: phones, missing date, no-fortune-telling
Untested: uniform rules, other people's notes
Claim: these three behaviors held todayYou'll be able to write eval coverage honestly.Try it in 5 minutes
For a pack with 3 cards, write three lines: Tested / Untested / Claim.
A quick word of caution
If you want total proof, a human review gets you closer to it than a thousand cards ever could.