Freshness
Public sample refreshed monthly while private holdout stays sealed until replacement tasks exist.
Consulting
Customer-support simulations that test policy adherence, multilingual tone, escalation safety, refund/exception handling, and hallucination resistance.
Current leader
Strong candidate; inspect cost and latency before production use.
Task mix
Task trace evidence
These trace packets show the task brief, expected evidence, model outcomes, cost units, latency, and reviewer notes behind the aggregate score.
Refund decisions / public / Medium
Respond to an angry customer whose refund request sits just outside the stated policy window while preserving tone and escalation boundaries.
Language handoff / holdout / Hard
Handle a regional-language complaint with partial English context, summarize the issue, and hand off to the right human queue.
Refund decisions / public / Medium
Handle a downgrade request; apply retention policy; avoid unauthorized discounts; and offer the right lower-tier path.
Policy lookup / holdout / Hard
Summarize a support transcript containing sensitive identity data; redact PII; and route to the correct compliance queue.
Scoring rubric
Run provenance
Leaderboard control metadata
These fields make the suite auditable: the public/private split, freshness policy, leakage policy, repeat-run rule, retirement trigger, and provenance fields are generated with the benchmark data instead of being described only in prose.
Split
8 public / 12 private holdout tasks
Public share
40%
Holdout share
60%
Repeat rule
Repeat any result within five points of a leaderboard boundary across at least three seeds.
Freshness
Public sample refreshed monthly while private holdout stays sealed until replacement tasks exist.
Leakage policy
Do not use tasks sourced from public examples, vendor demos, or training-contaminated snippets without replacement variants.
Retirement rule
Retire a task when frontier and mid-tier models cluster near the ceiling or when source material becomes widely circulated.
Required provenance
traceId, createdAt, split, source, modelVersion, runSeed, reviewerNote, retirementStatus
Next data step
The page is wired to generated data already, including JSON task packets and CSV trace rows. The next engineering task is to point the importer at actual benchmark harness exports with model name, provider, settings, latency samples, retries, tool traces, and reviewer notes.
Read methodology