Benchmark definition
Applicability does not mean evaluated; benchmark result/model score data is outside this UI contract.
Not recorded for this benchmark: what it does not measure, why it matters, motivation, gap addressed.
None recorded
None recorded
One undivided item set. No components or scenarios recorded.
What a result on this benchmark would be reported as. ctxdex does not carry results.
| Metric | Role | Direction | Unit |
|---|---|---|---|
Completion Under Policy Task completion under the benchmark-defined policy constraints. | Primary | Higher is better | Percent |
Partial Completion Under Policy Benchmark-defined partial completion while remaining within policy constraints. | Secondary | Higher is better | Percent |
Risk Ratio Source-defined ratio comparing unsafe/policy-violating behavior with benchmark-defined reference behavior; preserve exact source formula in metric parameters. | Secondary | Higher is better | Score |
Evaluate task completion jointly with benchmark-defined policy constraints; retain source policy metric formulas.
What the benchmark's harness provides and allows. These are properties of the environment, not model requirements, and applicability does not test for them.
Required conditions decide applicability. Relevant ones describe what the benchmark exercises and decide nothing.
51 of the 58 active, preview, experimental models meet this benchmark’s recorded requirements, at some scope. Applicable means the requirements are met, not that the model was evaluated.
View all 51 applicable models →Counted over 58 models in the default lifecycle scope (active, preview, experimental).
Every required condition, for the whole benchmark, is recorded as supported. Each line is one recorded condition and why it counts.
Every one of the 1 required conditions is recorded as supported.
MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)Every one of the 1 required conditions is recorded as supported.
MODALITY:INPUT:TEXTthe catalogue records SUPPORTED for TEXT (input)Applicability/relevance ordering only; never a performance ranking.
None recorded
None recorded
None recorded
13 contract fields are empty for every benchmark in this release and are not shown: applicability groups, conditional requirements, feature requirements, model relevance domains, required capabilities, openness summary, reference artifacts, interaction protocols, tool protocols, benchmark last major refresh at, short name, target expertise level, target population.