Skip to content
Clairos Learn

Evaluations and datasets · Lesson 9 of 18 · 6 min

Set a release threshold

A release threshold should be chosen before looking at candidate results. Include critical failure bounds, not only a single average target.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated AI Ops lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

A release threshold should be chosen before looking at candidate results. Include critical failure bounds, not only a single average target.

Interpret the evidence

Hold the candidate because 0.93 is below the predefined 0.95 gate.

A tempting mistake

Lower the gate after seeing the score and call the original goal achieved.

All names, measurements, prices, versions, and thresholds in this exercise are fictional training data. The evidence supports this bounded scenario, not a claim about a live provider.

Worked example and expected result
$ cat /opt/ai-lab/cases/aiops-evals-datasets-009.json
{
  "fixture": "Fictional training data; not a live measurement.",
  "required_pass_rate": 0.95,
  "candidate_pass_rate": 0.93,
  "critical_failures": 0
}

Exit status: 0. The command completed successfully in the training fixture.

$ jq .candidate_pass_rate /opt/ai-lab/cases/aiops-evals-datasets-009.json
0.93

Exit status: 0. The command completed successfully in the training fixture.

$ printf '%s\n' 'hold-below-threshold' > /home/learner/lab/aiops-evals-datasets-009-decision.txt
(no output; exit 0)

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Name the assumption that would have to change for “hold-below-threshold” to stop being the justified action. Do not silently replace missing evidence with a guess.

Explain it

What does the evidence in “Set a release threshold” justify?

Apply it elsewhere

A colleague concludes: “Lower the gate after seeing the score and call the original goal achieved.” What should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Review metric tradeoffsTry an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

  1. 01Compare evaluation runsControlled comparisons require the same cases and scoring rules. Separate an actual model/prompt improvement from a change in the evaluation itself.Practice
  2. 02Review metric tradeoffsPrecision and recall answer different questions. More retrieved items can improve recall while introducing irrelevant results; select the tradeoff for the actual task.Practice
  3. 03Inspect a data sliceSlice evaluation checks behavior on a meaningful subset. Keep slice size with the score and avoid generalizing a small or unrepresentative slice to all traffic.Practice