Module 3 · Benchmarks you can trust · Lesson 6
Contamination, saturation and broken tasks
How a benchmark stops measuring what it claims (leaked test data, saturated scores, underspecified tasks and wrong tests), traced through SWE-bench Verified from its 2024 re-annotation to its 2026 retirement, and how to audit and repair your own suite.
By the end of this lesson you can
- Explain construct, task and outcome validity, and test a benchmark's headline claim against them
- Detect and mitigate contamination with fresh or private tasks, held-out splits, canaries and memorisation probes
- Compute a saturation index for a leaderboard, and certify an all-fail task with oracle, empty-solution and infrastructure evidence instead of calling it hard
- Run a re-annotation pass that finds underspecified tasks and verifiers that reject correct work or accept wrong work, and fix what it finds