Lantern Evals HOW DO YOU KNOW IT WORKS
Suite dhs-variance-review · eval-v1 Target functions 1 Eval spend to date … Budget $100.00 Spent $532 at list, about $132 cash
Evaluation suite: dhs-variance-review/ Run: …/ Target: …/ Evaluators: 14 (11 code rules, 3 judges, 0 vibes)

Loading the held-out experiments.

Eight questions a tester typed. The prompt never saw them. The headline is pass^5 per experiment. The interval on pass^10 says how sure to be. The pooled rate is for comparing prompts during the climb. The dev set was never run at xhigh.

pass^5 per experiment…Two experiments of five runs.
pass^10, Wilson 95%…
Pooled pass^1 over runs…
Cost · median latency…

How we got here

Each row is two experiments of five runs on the same prompt. The highlighted row is what ships.

MilestoneSetJudgeEffort · cappass^5 eachpass^10 · Wilson 95%Pooled pass^1Cut at capCost

Rows through the corrected rerun used the old judge. The sweep used the xhigh judge, so 65 to 69 is a judge change. Prompt hash b44a9181 on every row. Dev was never run at xhigh.

The heatmap: test cases by runs, colored by the first scorer that failed

Rows grouped by tier. Ten columns, two experiments. A solid row is in pass^10.

Scorers run in table order. The letter is the first that failed. Hover a cell.

The dev climb, pass^1 by tier

Dev experiments only. A label marks a prompt change. Each prompt ran twice before it was judged, because the same prompt moves between runs.

VerifiedExploratoryNot available

What failed

Counts are for this pair only.

Latency by tier.

Every run in the headline pair, seconds from question to answer. Most of it is the model thinking. 500 s is the harness cap.

Latency is comparable only between passes with the same worker count.