evaluation-validity CAP-0014 · active

Whether the measurement made the finding

Whether a reported result describes the model or the way it was scored — the metric, the prompt format, the contamination, the baseline.

Tags: evaluation

A finding can be an artifact of how it was measured. A discontinuous scoring rule turns smooth improvement into an apparent jump; a baseline given a smaller budget loses; a benchmark in the training data flatters everyone. This capability collects claims about when a measurement stops reflecting the thing it names. It sits oddly beside the others because it is not a property of a model, but every claim in this index rests on some measurement, so it is the one capability whose failures propagate everywhere.

What counts as this capability

Scope boundary used when deciding whether a paper is really about this capability, rather than merely mentioning it.

In scope when the paper's finding is about the measurement rather than the model: showing a result changes or disappears under a different metric, prompt format, baseline budget, or decontaminated split. NOT in scope: a benchmark paper reporting how models score, which belongs to whichever capability it tests; and not general "we need better evals" position papers with no demonstration.

Claims

Techniques

  • Detect benchmark leakage with a code-specific membership claprocess
    Fine-tune a shadow model on part of a benchmark to label members and non-members, then train a classifier on expert features (pass rate, CodeBLEU, edit distance, perplexity) fused with CodeBERT embeddings to predict whether a benchmark item
  • Deterministic checks before LLM judgesprocess
    Wire linters, test suites and schema validators into the agent's loop before adding any model-based judgment.
  • Report operational acceptance and reference reconstruction sprocess
    Use parser, domain-conformance, planner, VAL and LLM-critic checks as the online stopping criterion, but compute renaming-invariant structural match and semantic equivalence against curated reference problems offline as a separate benchmark
  • Report per-family spread, not an aggregate agent scoreprocess
    Split an agent benchmark into skill-isolated families with verifier-computed gold (canonical SQL, exact DAG schedule, closed-form lambda) and report per-family accuracy plus token cost from one instrumented run instead of a blended score.
  • Score proof answers with a binary pedagogical rubric, not n-process
    Replace lexical-overlap scoring with the mean of six binary per-response criteria (step enumeration, notation correctness, worked example, sub-question coverage, explanation depth, proof-step granularity).
  • Unify offer schema and chooser, then flag the treatmentprocess
    Apply the policy treatment as post-parsing boolean flags over one shared message schema and one shared buyer decision rule, average repeated generations within profile-condition, and bootstrap over profiles rather than generation rows.

Sources

Every paper, post or observation behind this capability. Ones cited by a claim show the claim and its stance; ones filed directly are about the capability but have no claim drafted from them yet. Open one to add support or contest it.

Suggest a change

Capabilities are a way of carving up the subject, and carvings are arguable. Say so if this one is wrong — especially a proposed one, which a pipeline added because several papers used the same framing, not because anyone decided it was right.