Find the broken tasks before your model trains on them.
Every task is checked, run and repaired, then routed to ready, needs a human, or failed.
-
Deterministic checks 38 checks, no findingsPass
-
Rubric review Correct alternative answers are rejectedFlag
-
Reference run Shipped solution scores 1Pass
-
Do-nothing run Scores 0, as it shouldPass
-
Execution probe An equally valid reason scores 0 (227 of 232 points)Proven
We audit public benchmarks. Here's what we found.
- 6/30 of DeepSWE's hardest tasks reject a correct solution
- 4/5 Terminal-Bench pilot tasks with a critical or major defect
- 53 tasks audited across three public benchmarks, with every report published
Filed upstream: 3 issues on Terminal-Bench #2248 #2249 #2250
Spot the broken verifier.
Each of these looks fine on a read. Each one scores agents wrongly.
TaskCustomer #4821 wants their unshipped order cancelled and the payment refunded.
def verify(db, run):
order = db.orders.get(4821)
assert order.status == "cancelled"
calls = [c.name for c in run.tool_calls]
assert calls == ["get_order", "cancel_order", "refund_payment"]
assert db.refunds.count(order_id=4821) == 1
Line 5 demands one exact sequence of tool calls. An agent that refunds before it cancels ends in the same correct state and still scores zero.
You caught 0 of 3.
Our review stack runs these checks on every task, before anything trains on it.
Pick your starting point.
- 01 I build RL environments or benchmarksTasks, verifiers and model runs, checked before they reach a training run or a leaderboard.
- 02 I run a data or annotation teamScale quality control across your contributors without scaling headcount.
- 03 I ship a GenAI productAn automated QA loop that catches bad outputs before your users do.
Five layers. Every task.
Code checks first. Models judge only what code can't. Nothing passes until it has been run.
- L1
Deterministic checks
Schema, config, answer leaks, seed data.
- L2
Dimension agents
One rubric per quality dimension. Three reviewers, two votes to fail.
- L3
Execution
The reference must pass. A do-nothing run must fail.
- L4
Trajectories
Why models failed, and whether they gamed the checks.
- L5
Repair and route
Safe fixes applied. Ready, needs a human, or failed.
"Define the tolerance, measure against it, and don't ship what fails."
Sheharyar Akhtar, founder. Built review infrastructure for frontier AI lab training programs. More about us
Send us 20 tasks. We'll show you which ones are broken, and why.
A free 20-task pilot. Book a 20-minute call to start.