What eyewitness-ID reform teaches AI evals. A 1985 lineup change doubled a justice-system metric without making one witness better at telling guilty from innocent, and a hundred-year-old branch of statistics says exactly why.
In 1985, two psychologists ran a lineup experiment that looked like a gift to the American justice system.
The setup was the one every cop show has taught you to picture: a witness, a row of faces studied all at once. Lindsay and Wells called that the simultaneous lineup, and in their data it was alarming. Witnesses picked the actual culprit 57% of the time, but when the culprit was not there and the lineup was all innocent fillers, they still pointed at someone 42% of the time. So the researchers tried showing the faces one at a time, a yes-or-no on each, no going back. False identifications collapsed: 42% down to 17%. The catch rate barely flinched, 57% to 50%. Scored the way the field scored lineups then (correct IDs divided by false IDs, the “diagnosticity ratio”), the sequential lineup came out at 2.94 against the simultaneous lineup's 1.36. More than twice as diagnostic.
That number became policy. In October 1999, pushed by DNA exonerations full of confident, sincere, wrong eyewitnesses, Janet Reno's Justice Department published the first national guide on eyewitness evidence and recommended sequential presentation where practical; New Jersey adopted it statewide in 2001, and departments and courts followed for two decades.
Here is the part that matters for anyone who ships a model behind an eval dashboard. The reform did not make eyewitnesses better at telling guilty from innocent. It made them more reluctant to choose. Those are different things, a hundred-year-old branch of statistics exists precisely to keep them apart, and the failure to keep them apart is the most common way an AI team fools itself today.
The statistics is signal detection theory, born in WWII radar rooms. (“ROC curve” literally stands for receiver operating characteristic, after the radar receiver operators deciding whether a blip was a bomber or a goose.) It was brought into psychology by Green and Swets, whose 1966 book is still the foundation everyone cites.
Its central move is to split any yes/no detector (a radar, a witness, a spam filter, a safety classifier) into two quantities that feel like one thing and are mathematically independent:
The consequence is unforgiving: moving the criterion slides you along a fixed curve; it never moves the curve. Demand more evidence before saying yes and you will make fewer false accusations and fewer correct catches, in an exchange rate the curve already dictates. You have not improved the detector. You have rationed the same information more cautiously. Tom Fawcett's widely used 2006 primer on ROC analysis makes the formal point: AUC is a ranking measure. Rescale every score, squash them through any order-preserving function, and the curve does not budge; all that changes is where a given cutoff lands. Only more separating information (a higher d′, a curve pushed up-and-left, fewer of both errors at once) is a better detector. Everything else is seating arrangements.
Now reread 1985 with the two knobs in hand. Under sequential presentation, correct IDs and false IDs both fell (57 to 50, 42 to 17). Both falling together is the signature of a criterion shift: a witness who needs more certainty before choosing anyone. And the diagnosticity ratio nearly doubled not because witnesses saw more clearly, but because the denominator fell faster than the numerator. The reassuring number went up for a reason that had nothing to do with anyone getting better.
It took the field decades to sort its reforms into the right SDT buckets, and the sorting is the story.
Reform one: unbiased instructions. Tell the witness, before the lineup, that the culprit “may or may not be present,” a practice the National Institute of Justice lists among its science-based lineup procedures. Read through the SDT lens, this is the purest criterion move in the canon: the warning licenses not choosing, witnesses get more conservative, false IDs drop. Nothing about the witness's underlying memory (their ability to tell the culprit from a stranger) has changed. It is a good policy and it is not an accuracy gain, and holding both thoughts at once is the whole discipline.
Reform two: the sequential lineup, the big one, the 1985 result, the DOJ recommendation. In 2012, two independent lines of work finally scored it on the right axis. Palmer and Brewer ran a compound signal-detection reanalysis across 22 sequential-versus-simultaneous experiments; their title is the finding: “Sequential Lineup Presentation Promotes Less-Biased Criterion Setting but Does Not Improve Discriminability.” Witnesses were not discriminating better. They were choosing less. The same year, Mickes, Flowe, and Wixted did the obvious-in-hindsight thing: instead of scoring each procedure at the single operating point witnesses happened to use, they traced full ROC curves by sweeping across witness confidence (Journal of Experimental Psychology: Applied). Compared curve-to-curve, the simultaneous lineup was, if anything, diagnostically superior, the opposite of the reform's premise. Wixted and Mickes's 2014 Psychological Review model even supplies a mechanism: seeing faces side by side lets a witness discount the features all the fillers share and weight the ones that discriminate. (Honesty requires the footnote: the lineup's filler structure complicates the clean SDT mapping, and the ROC approach drew real controversy; this is the dominant modern view with a live minority, not scripture.)
Reform three is the one that generalizes: record confidence at the first identification. In 2017, Wixted and Wells published a synthesis in Psychological Science in the Public Interest with a finding that surprised almost everyone, including the reformers: under “pristine” conditions (first test, fair lineup with one suspect, double-blind administrator, confidence recorded immediately, before any feedback), high-confidence initial identifications are surprisingly accurate, and low-confidence ones are error-prone. The conditionality is load-bearing: confidence is informative at the first test only, before feedback and repetition contaminate it, and a follow-up commentary by Mickes, Clark, and Gronlund the same year sharpened the message's limits. But notice what kind of reform this is. Instructions and sequential presentation tried to change the detector's behavior. Recording confidence changes the measurement: a graded confidence readout is what lets you trace the whole ROC curve instead of staring at one overt yes/no point. The reform with the most durable payoff was not a knob turn at all. It was: stop grading the detector at a single point.
That is the lesson the justice system paid decades for. A field reduced its visible error, celebrated a single-operating-point metric that improves automatically when people merely answer less, wrote the procedure into policy, and the eventual fix was not a better procedure but a better measurement, one that sees the curve.
If you build or evaluate models, you have seen this metric. It said: “hallucinations down 40%.” Or “harmful completions cut by two-thirds.” Or “false positives halved.” And the model felt better.
Sometimes it was. Often it is the sequential lineup again: the same detector, more reluctant.
The mapping is not a metaphor; it is the same mathematics. A classifier's ability to separate harmful from benign, hallucinated from grounded, spam from ham, is its d′, its ROC curve. The refusal threshold, the confidence cutoff, the “only answer when sure” setting is a criterion, a point on that curve. Raise it and the visible error falls, reliably. Just as reliably, the other error rises: benign requests refused, correct answers withheld, recall quietly bleeding out. Cut a safety filter's false-positive rate without touching the model and you have re-seated yourself on the same curve, at the cost of misses someone else's dashboard will discover. The over-refusal literature (XSTest is the canonical benchmark, 250 prompts that look dangerous while being perfectly benign) exists precisely because “we made the model safer” so often meant “we moved its criterion” and nobody had priced the false alarms.
Three traps follow, each with an eyewitness twin:
One caveat, so the pendulum does not overswing: AUC is not a god-metric. On heavily imbalanced data (and rare-harmful-event safety data is exactly that) it can flatter, and your test distribution has to resemble your traffic. The commandment is not “worship AUC.” It is measure the curve, not one point on it.
Here is the tool to carry out of this essay. When anyone (a vendor, a paper, your own team, yourself) claims a detector “got better,” ask two questions, in order:
Question one: did the criterion move? Did the answer rate change, more refusals, fewer IDs, a stricter cutoff? If yes, expect the two error types to have moved in opposite directions: false alarms down, misses up, or the reverse. That is a criterion shift. It may be excellent policy (Blackstone's “better that ten guilty escape than one innocent suffer” is a criterion, chosen out loud, for stated moral reasons), but it is a choice about which mistake to prefer, not an improvement, and it should be reported in the language of choices.
Question two: did d′ move? At a fixed operating cost, same refusal rate, same review budget, same answer rate, did both errors fall? Did the ROC curve lift? That, and only that, is a better detector. It comes from better information: better features, better training data, better grounding, an independent second signal, never from the knob.
The rule of thumb that dissolves most eval theater in one sentence: a single number at a single operating point cannot distinguish question one from question two. If the claim arrives as one dot (one accuracy, one harmful-rate, one false-positive percentage) it is a criterion story until a curve proves otherwise. Ask for the curve, or two operating points, or the confidence distribution. If none exist, the honest sentence available is not “the model is better.” It is “we chose a more conservative operating point,” a perfectly respectable sentence that has the additional virtue of being true.
The eyewitness field's quarter-century detour ended when it stopped scoring witnesses at one point and started tracing curves, and discovered that its flagship reform had been a threshold move wearing an accuracy costume, while its sleeper reform, recording confidence, had been the real thing all along: not a better witness, but a measurement finally worthy of the question. Your evals are in year two of that story, with the literature already published and waiting. The detector you cannot improve by moving its threshold is every detector you own. What you can improve, starting with the next report you write, is whether you can tell the difference.
A single number at a single operating point cannot tell a more reluctant detector from a better one. Ask for the curve.
That is the problem the Agent Rating Protocol is built for: a way to rate and rank agents that refuses to collapse a detector to one blessed operating point, so a rating reflects how well an agent actually separates good from bad, not how conservatively it was tuned the day it was scored. It is one layer of the Agent Trust Stack, the harness for making agent behavior verifiable, rateable, and claimable rather than taken on the leaderboard's word.
Read the Theory of Agent Trust
pip install agent-rating-protocol · npm install agent-rating-protocol
Full trust stack: pip install agent-trust-stack · npm install agent-trust-stack