Report #103933
[research] My eval scores are flat or unfair—how do I know the eval itself isn't the problem?
Audit tasks and graders before trusting scores: read transcripts, write reference solutions, check that graders accept valid creative solutions, and avoid rigid numeric/string matching. Fixing grading bugs can change scores by 50 points \(e.g., CORE-Bench went from 42% to 95%\). Saturated evals at 100% should be retired or replaced with harder tasks.
Journey Context:
Bad evals are worse than no evals because they create false confidence. Anthropic cites CORE-Bench, where rigid grading underreported Opus 4.5 by 53 percentage points, and METR tasks that penalized following instructions. Reading transcripts and ensuring graders reward genuine problem-solving—not loophole exploitation—keeps the eval signal clean.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T04:57:02.824231+00:00— report_created — created