Skip to main content
v2026.11,858 entries · CC-BY 4.0
NIKOLAI elementN6 · Mitigations and securityProposednikolai-v0.1

Coverage level

NIKOLAI proposes Coverage level as a graded controlled-value axis stating the scope of content or behavior a safeguard is designed to catch, kept independent of how robust the safeguard is against circumvention. This is an unsourced NIKOLAI editorial synthesis. It must not be conflated with an evaluation's own test-category coverage (see divergence_note) or with a coverage *date* (a distinct property).

This is CASRAI's own proposed definition, not a definition any named organisation has agreed to. See what NIKOLAI is and is not.

Source of record

Where this definition comes from

Crosswalk

How named organisations use this concept

Every row below is a shadow mapping. It is CASRAI's own reading of a published document. No lab, evaluator or regulator named here has declared, endorsed, or been consulted on this mapping. That will change only when an organisation files its own Mapping Declaration — see the non-endorsement policy.
OrganisationTheir term, as publishedMatchSource
Anthropic
Anthropic Risk Report, August 2026
"Coverage — the domain of usage a classifier is trained to catch"; Fable 5's classifier covers "the vast majority of potentially dual use usage relevant to research biology"; "100% of a generated research-biology probe set versus 17% for the narrower classifier"exact
confidence: high
Anthropic Risk Report, August 2026
Google DeepMind
Gemini 3.7 Flash FSF Report
"Coverage: 'assuming threat actors don't try to circumvent these safeguards, how much assistance would they get from the model'"close
confidence: medium
Gemini 3.7 Flash FSF Report
Frontier Model Forum
FMF Third-Party Assessments
"Evaluation coverage: 'identifying test categories, particular workflows, or user skill levels.'" This is coverage of an *evaluation*, not a safeguard.
False friend: FMF's "coverage" here names what an evaluation tests, not what a safeguard blocks. See divergence_note.
none
confidence: medium
Frontier Model Forum, Third-Party Assessments

Related, not mapped

Pointers that are not crosswalk claims

These sources mention this concept but do not define or map it clearly enough to count as a crosswalk row — noted here so the research is visible without overstating it as a mapping.

Divergence

Where sources materially disagree

FMF's "Evaluation coverage" is a false friend for this element: it describes the scope of an *evaluation* (which test categories, workflows, or user skill levels are probed), not the scope of a *safeguard* (what content or behavior a classifier is trained to catch). NIKOLAI's coverage-level element tracks safeguard scope only; evaluation coverage is a distinct concept that belongs under the evaluation record-type (N5), and the two must not be crosswalked to each other. See ALIGNMENT-MATRIX.md §3 E4, FMF row {FMF32}.

Gap

Anthropic and GDM independently separate coverage from robustness, which supports making them two elements. Anthropic's disclosed year-long gap (human-feedback vendor traffic "ran without blocking biological classifiers") was a coverage failure by deployment surface, not a robustness failure {RR}.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →