Result records

Leaderboard

One row per model × harness, one board per benchmark version. Only site-verified result records are shown. Safety vetoes have their own columns and never enter the ranking.

No verified results yet

First holdout round in preparation. This board is generated from registry/results/; it populates when the first reviewed result records are merged. No placeholder or demonstration scores are shown.

Boards

Columns

ColumnDefinition
ModelModel id and service snapshot
HarnessRegistered harness id and version
Group lettersCompact letter display from pairwise paired comparisons on the same tasks, Holm-adjusted; rows sharing a letter are not shown to differ, and a row can carry several letters
pass^3Share of holdout tasks passed in all three runs, with its Clopper–Pearson interval; the primary ordering key
pass@3Share of holdout tasks passed in at least one of three runs
Instabilitypass@3 − pass^3
ExamPassed (every task, all three runs, no veto) or not passed, with the number of tasks and, when passed, the claimable lower bound 0.051/n
LevelNot issued: methodology 0.1.0 sets no level threshold, so no level is issued
Task pass rateShare of passing runs per task, averaged over tasks, with its BCa bootstrap interval
Continuous scorePassed checkpoints / checkpoints per run (0 on a veto), averaged over runs, then tasks; never compared across families; not an ordering key
CalibrationCalibration subset, reported separately
VetoesRuns with a veto, by category (fabricated evidence, altered input, corrected value, executed injection, unsafe advice) and by constraint X.1–X.4; any hit fails the run and marks the row
Reference vetoesHits on veto-flagged grading references, keyed by X capability
ErrorsRun errors by attribution; every error is a failed run, never re-run and never removed
Cost per successTotal amount over all runs / passing runs, under the price table version named on the row. The amount is the price a buyer pays under that table, not the resources a run consumes, and it compares only within one price table version and time window. It orders adjacent rows that carry an identical set of group letters. Self-hosted and open-weight subjects: amount not applicable, and they take no part in that order

Rows are ordered by pass^3; among adjacent rows with an identical set of group letters, rows with an amount are ordered by cost per success. Amounts compare prices paid, not resources used. Overlapping intervals do not define a group. Missing fields display "—", never 0; a dimension a family does not support shows "not applicable". Calibration tasks never enter family averages. Results under different benchmark versions are not comparable. See intervals and the order of rows.

Why rows are model × harness

A leaderboard row is a model inside a harnessThe same model under two harnesses produces two separate rows. Each row is tied to one benchmark version. Safety vetoes are a separate column that never enters the ranking metric.Model M · snapshotModel M · same snapshotHarness H1 @ vHarness H2 @ v××row 1 · benchmark @ versionpass^3 · pass@3 · costrow 2 · benchmark @ versionpass^3 · pass@3 · costvetoes X.1–X.4vetoes X.1–X.4the gap between rows is a measured quantity, not a pass mark