Source of record
Where this definition comes from
Google DeepMind Frontier Safety Framework v3.1, glossary, p.20
“Safety Cases: are an assessable argument showing how severe risks associated with a model's CCLs have been reduced to an acceptable level. (glossary, p.20)”
https://storage.googleapis.com/deepmind-media/DeepMind.com/Blog/strengthening-our-frontier-safety-framework/frontier-safety-framework_3-1.pdfGemini 3.7 Flash FSF Report, p.41
“Our safety case relies on two evaluation suites and assumes that AI deployments will feature oversight similar to that of human employees (p.41)”
https://storage.googleapis.com/deepmind-media/gemini/gemini_3-7_flash_fsf_report.pdf
Crosswalk
How named organisations use this concept
Every row below is a shadow mapping. A shadow row is CASRAI's own reading of a published document. No lab, evaluator or regulator named on a shadow row has declared, endorsed, or been consulted on it. That changes only when an organisation files its own Mapping Declaration.
| Organisation | Their term, as published | Match & verification | Source |
|---|---|---|---|
| AnthropicShadow mapping Anthropic Risk Report, August 2026 | “Claim graph with aggregation types (§2, see C1 above). The Risk Report does not use "safety case" as its own label in the brief's record.” | closeCL confidence: medium | Anthropic Risk Report, August 2026 |
| OpenAIShadow mapping OpenAI Preparedness Framework v2 | “"Safeguards case" is used in Table 2 ("require the Safeguards case to be robust to the discovered capability and/or propensity") and "not defined separately".” | noneDU confidence: medium | OpenAI Preparedness Framework v2 |
| Google DeepMindShadow mapping Google DeepMind Frontier Safety Framework v3.1 / Gemini 3.7 Flash FSF Report | “Safety case definition (glossary); "Residual risk assessments will be supplemented with a safety case when a model reaches a CCL" (glossary). The report says "Our safety case relies on two evaluation suites and assumes that AI deployments will feature oversight similar to that of human employees" (p.41) but does not define it there.” | exactEQ confidence: high | Google DeepMind Frontier Safety Framework v3.1 |
| MetaShadow mapping Meta Advanced AI Scaling Framework v2 | “"Developing safety cases in advance of models exhibiting capabilities related to our enhanced evaluations." (§4.2.3); no format, author or reviewer given.” | noneDU confidence: medium | Meta Advanced AI Scaling Framework v2 |
| UK AI Security Institute (AISI)Shadow mapping UK AISI safety case templates (discovery) | “UK AISI safety case templates (inability argument) [UV].” Citation tag {DEU} does not appear in the supplied sources table and no URL could be resolved without inventing one; left blank rather than fabricated (confirmed still open in ALIGNMENT-MATRIX.md §6 item 7). Match type 'close' is inferred from context (an 'inability argument' template is directly analogous to a safety case) per the UV translation rule, not confirmed against primary text. | closeUV confidence: low | UK AISI safety case templates (citation tag {DEU} unresolved in sources table) |
| Frontier Model ForumShadow mapping Frontier Model Forum: Third-Party Assessments | “Safety case analysis as a form of holistic review (see C1 above).” | closeCL confidence: high | Frontier Model Forum: Third-Party Assessments |
What do these codes mean?
- exact
- The source term is equivalent to this element
- close
- The source term is close but not equivalent to this element
- broad
- The source term is broader than this element
- narrow
- The source term is narrower than this element
- none
- No mapping claim — used for false-friend and declared-but-undefined rows
- EQ
- Equivalent
- CL
- Close
- BR
- Source is broader than the element
- NR
- Source is narrower than the element
- FF
- False friend — same or similar label, different meaning
- DU
- Declared but undefined by the source
- UV
- Unverified
Divergence
Where sources materially disagree
Added to the candidate list (ALIGNMENT-MATRIX.md §5) specifically because 'safety case' has an inconsistent operational status across sources: fully defined and instanced by Google DeepMind, used as an undefined trigger term by OpenAI and Meta (DU), not used as a label at all by Anthropic despite an equivalent claim-graph structure existing, and known only via discovery for UK AISI.
