How the four signals are computed
The technical companion to the four interpretive signals. This formalizes how each one is calculated, the fields it depends on, and how it rolls up across the corpus. Adapted from Appendix H.1 of the paper.
See also: the Quickstart introduces what each signal means in plain language. This page is the precise definition behind it.
The result triple
Every signal is computed over a result triple :
- : a canonical model identifier,
- : a metric-path through the rollout hierarchy (family → composite → benchmark → split),
- : a metric.
is the set of all such triples in the corpus, and the set of canonical benchmarks. For any field and triple :
and is defined analogously for a benchmark and its Auto-BenchmarkCards record.
Reproducibility
In plain terms. For each result, we check whether the small set of fields needed to re-run the evaluation are present. If any are missing, we flag the result.
The minimal reproducibility sub-schema is:
For agentic evaluations, is extended with , , and .
A result is flagged as a reproducibility gap if any required field is missing:
That is, only when every field in is populated. The interface lists the specific missing fields, .
Corpus-level reproducibility is the share of flagged triples, and per-field reporting uses the missingness rate:
Reporting completeness
In plain terms. For each benchmark, we count how many of the 28 schema fields are populated. Present-or-absent fields score 0 or 1; fields that contain sub-items score the fraction of sub-items populated. The completeness score is the average across all 28 fields.
Let be the operationalized schema with fields, ingested from Auto-BenchmarkCards and EEE plus the reserved Evaluation Cards fields. Each field has a coverage type , and the per-field score is:
where is the set of sub-items under a partial-coverage field. For example, a partial field with 4 sub-items, 2 of which are populated, scores .
The completeness score for a benchmark is the unweighted mean across fields:
The interface surfaces alongside the count of fully missing fields, . Across the corpus we report the median per-benchmark completeness, , and per-field population rates, .
Completeness and reproducibility are distinct: , so a result with no reproducibility gap may still have low completeness.
Provenance
In plain terms. For each reported score, we surface three things: who reported it (first-party, third-party, or collaborative), whether anyone else also reported the same score, and any risk categories associated with the benchmark.
Let be the evaluator relationship for triple . For a triple , the set of records reporting it is .
A score is first-party-only if every report comes from the model developer:
The multi-party indicator is when , and otherwise. Risk annotations are propagated from the Auto-BenchmarkCards risk-mapping component: each benchmark carries a set of risk categories . These are shown as attention cues in the interface and do not enter a numerical score.
Comparability
In plain terms. For each triple with at least two reports, we check whether reported scores differ by more than 5% of the metric's range. We do this two ways: across setups for the same party (variant divergence) and across different parties (cross-party divergence). Either one triggers a flag.
Let be the metric's native scale and the divergence threshold.
Variant divergence. For a triple with multiple reported setups (differing in fields such as , tool configuration, or agentic scaffolding), let be the set of distinct variants and the score under variant . It is flagged when the spread exceeds :
The differing fields are surfaced as the comparability annotation.
Cross-party divergence. Let be the set of reporting parties and the score reported by party (averaged across variants within a party if needed). It is flagged when more than one party reports the triple and the spread exceeds :
The underlying setup differences across parties are rendered alongside the divergence.
Combined flag. The overall comparability signal is the maximum of the two:
The threshold is applied uniformly across metrics; metric-specific thresholds are a candidate extension.
One thing to keep in mind
None of these signals is a grade. Evaluation Cards assigns no letter grades, pass/fail thresholds, or completeness rankings. When a field is omitted, it lowers the completeness score, may trip the reproducibility, provenance, or comparability signals, and is shown to readers directly. The intent is to make reporting choices visible, not to enforce a particular reporting standard.
Adapted from Appendix H.1, "Computation of Interpretive Signals" of the paper.