Understanding

Case Drilldown

Solves: judging one answer, and deciding whether the judge got it right.

Watching — a candidate behavior we are tracking, not yet a published pattern.

watching emerging established contested fading 8 sightings since Aug 2024 seen in 2 different contexts
Ask an assistant about this pattern Ask ChatGPT ↗Ask Claude ↗

Case Drilldown is one example examined on its own. The person reads both answers and the reasoning behind the verdict of the judge, the model that scored them. They can overrule the verdict with a note, and they can keep the case as a permanent test so the failure is caught next time. Overrules are counted, because they show where the judge and humans disagree.

When to Use It

  • A verdict looks wrong and someone needs to say so
  • A failure should never happen again
  • The team wants to know how much to trust the judge

When Not To

  • Cases are read-only; then it is a report, not a drilldown
  • There is no judge reasoning to show
  • Overrules go nowhere; then collect them elsewhere

Three views

The exchange between the human, the agent and the system the agent acts on; who holds each part of it; and the component that implements it.

01 · the interaction
human agent system trace store · judge model opens one case fetches the input, the output, the verdict and the reasoning returns the trace shows the case, the verdict and where the judge disagreed overrides the verdict or promotes the case records the override; adjusts the judge
02 · who holds what
human interface agent The case: One input and the answers it produced 01 The case Judge verdict: Pass or fail, with the reasoning in words 02 Judge verdict Override: The person sets their own label, with a note 03 Override Promote: The case joins the permanent test set 04 Promote Disagreement count: How often humans overrule the judge, kept in view 05 Disagreement count
human interface agent The case: One input and the answers it produced 01 The case Judge verdict: Pass or fail, with the reasoning in words 02 Judge verdict Override: The person sets their own label, with a note 03 Override Promote: The case joins the permanent test set 04 Promote Disagreement count: How often humans overrule the judge, kept in view 05 Disagreement count
  1. 01 The case One input and the answers it produced
  2. 02 Judge verdict Pass or fail, with the reasoning in words
  3. 03 Override The person sets their own label, with a note
  4. 04 Promote The case joins the permanent test set
  5. 05 Disagreement count How often humans overrule the judge, kept in view
03 · the component

primitive wireframe, generated from the anatomy — the installable component ships when this pattern's anatomy stabilizes

Field Notes

JUN 17 · Paper · via arXiv Case DrilldownComparison View

21 judge models agreed with themselves and still carried bias

A score you cannot open is a score you cannot trust. The judge's reasoning, and the cases where humans overruled it, belong on the screen beside the number.

MAY 8 · Paper · via arXiv Case DrilldownEval Set Authoring

A paper gives reviewers the number of labels a judge needs

This is the number behind "calibrate with a few labels". A product can tell the reviewer how many cases to label before the judge can be trusted. Not all of them, and not none.

JUL 29 · Clipped · via LangChain blog Case DrilldownEval Set Authoring

LangSmith scores its judge against the team's own grades

The alignment score is the trust signal. A judge version with a number beside it, measured against the team's own grades, is something a product manager can decide to rely on.

AUG 15 · Clipped · via Freeplay blog Case DrilldownProduction Drift

Freeplay asks the reviewer to agree or disagree, ten cases at a time

Ten at a time is the right unit. It is enough to calibrate a judge and small enough that a designer will do it over coffee. That is the difference between a habit and a study.

Documented sightings (4) — anatomy-mapped observations from vendor materials
OpenAI

A person annotates a graded run; the annotations feed prompt optimization, so the overrule changes the prompt, not only the label.

OpenAI · Oct 6, 2025
LangChain (LangSmith)

Human and judge scores sit side by side, sorted to the disagreements; a correction becomes an example the judge is tuned on.

LangChain blog · Jul 29, 2025
Freeplay

Score and explanation on each example; the person agrees or disagrees, and the alignment score decides when the judge is trusted.

Freeplay blog · Aug 15, 2024
Confident AI (DeepEval)

Metric alignment reports false positives and negatives against human labels, so the team knows which metrics to trust.

Confident AI on GitHub · Sep 11, 2026

Side by Side

Anatomy part OpenAILangChain (LangSmith)FreeplayConfident AI (DeepEval)
The case one traceone exampleone exampleone test case
Judge verdict grader verdict against criteriajudge scoremodel score with explanationmetric score with reason
Override human annotationhuman score, stored as a few-shot exampleagree, disagree, or revisehuman annotation
Promote to datasetgoldens
Disagreement count alignment score per judge versionalignment score per versionmetric alignment report

Tensions & Failure Modes

  • Silent overrules: a label changed with no note teaches the team nothing. The note is the point.
  • Judge calibration: a few human labels tune the judge; too many and humans are doing the judge's job. Sample where the judge is least sure.
  • Promote it all: a regression set that takes each failure becomes slow and stale. Promotion should be a choice, not a reflex.

The Story So Far

  1. Sep 16, 2026 drift: too-early → quiet (30d sightings 0 → 0)
  2. Sep 11, 2026 Added to the Watching list from the prompt-evals brief and the 2026-09-11 vendor pass; the Chromatic review loop shapes the comparison and release entries.

Related Patterns