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 |
|---|---|---|---|
Requirement Satisfaction Rate Canonical Batch-2 metric code REQUIREMENT_SATISFACTION_RATE; benchmark-specific formula/parameters remain on benchmark_metric and methodology records. | Primary | Higher is better | Percent |
None recorded
What the benchmark's harness provides and allows. These are properties of the environment, not model requirements, and applicability does not test for them.
None. Static prompts and answers.
Required conditions decide applicability. Relevant ones describe what the benchmark exercises and decide nothing.
No required conditions recorded. Every model is Not recorded for this benchmark.
This benchmark records no required conditions. Without requirements, no model can be shown to meet them, so every model is Not recorded. This is correct, not missing data.
None recorded
None recorded
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.