Examples
Examples from published documents
- "Under California's Transparency in Frontier AI Act (TFAIA), this FGF is our Frontier AI Framework" (OpenAI Frontier Governance Framework, section 1)
- A system card can count as the statutory report: a developer that publishes the required information "as part of a larger document, including a system card or model card, shall be deemed in compliance" (California SB 53, section 22757.12(c)(3))
- An explicit non-mapping: Anthropic uses 'catastrophic risk' "in its plain meaning rather than adopting any specific statutory definition" (Anthropic RSP v3.4, fn 1)
Counter-examples
Not to be confused with
- A NIKOLAI crosswalk row is not a mapping declaration: it is CASRAI's own reading of a source, and the mapped party has neither made nor endorsed it.
Related terms
Related AI safety terms
Terms defined under this element that are not NIKOLAI elements themselves, each as the cited document uses it. Every term is also listed in the AI safety glossary.
- Alternative adequate means
- Alternative adequate means is the route by which a general-purpose AI provider that has not signed a chapter of the EU GPAI Code of Practice shows, in another way, that it meets the AI Act obligations that chapter covers.
- Source: EU GPAI Code of Practice (landing page)
- Declaration of intent (federal incident-reporting route)
- A declaration of intent, under California SB 53 and New York's RAISE Act, is a frontier developer's notice to the state regulator that it will meet the incident-reporting duty by complying with a designated federal law, regulation or guidance document.
- Source: California SB 53
Source of record
Where this definition comes from
California SB 53, 22757.13(i)(1)
“A frontier developer that intends to comply with this section by complying with the requirements of, or meeting the standards stated by, a federal law, regulation, or guidance document designated pursuant to subdivision (h) shall declare its intent to do so to the Office of Emergency Services.”
https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB53OpenAI Frontier Governance Framework, §1
“Under California's Transparency in Frontier AI Act (TFAIA), this FGF is our Frontier AI Framework”
https://cdn.openai.com/pdf/e37d949b-8c9f-4d76-b99e-4272f4631a7e/openai-frontier-governance-framework.pdf
Crosswalk
How named organisations use this concept
| Organisation | Their term, as published | Match & verification | Source |
|---|---|---|---|
| OpenAIShadow mapping OpenAI Frontier Governance Framework / Preparedness Framework v2 | “"Under California's Transparency in Frontier AI Act (TFAIA), this FGF is our Frontier AI Framework"; "Under the European Union's General-Purpose AI Code of Practice (the EU CoP), this FGF serves as our publicly available summary of OpenAI's Safety & Security Framework" (§1). PF fn 2: "our adoption of Capability Reports and Safeguards Reports parallels Anthropic's updated RSP."” Also cites Preparedness Framework v2 for the fn.2 parallel-to-Anthropic remark. | exactEQ confidence: high | OpenAI Frontier Governance Framework |
| xAIShadow mapping xAI Frontier AI Framework (30 Jun 2026 / 31 Dec 2025) | “June 2026 fn 1: "Terminology used in the The Safety and Security Chapter of the General-Purpose AI Code of Practice developed under the EU AI Act." Dec 2025: claims compliance with TFAIA, Cal. Bus. & Prof. Code 22757.10 et seq.” The xAI framework's PDF metadata reads 'Privileged/Confidential DRAFT working FRAMEWORK DOC'; draft-vs-final status unresolved. Also cites xAI's 31 Dec 2025 Frontier AI Framework for the Dec 2025 TFAIA-compliance claim. | exactEQ confidence: medium | xAI Frontier AI Framework (30 Jun 2026) |
| EUShadow mapping EU GPAI Code of Practice (landing page) | “Obligations under unsigned chapters shown through "alternative adequate means" (landing page).” | closeCL confidence: medium | EU GPAI Code of Practice (landing page) |
| California SB 53Shadow mapping California SB 53 | “"A frontier developer that intends to comply with this section by complying with the requirements of, or meeting the standards stated by, a federal law, regulation, or guidance document designated pursuant to subdivision (h) shall declare its intent to do so to the Office of Emergency Services." (22757.13(i)(1)). Also: a system or model card containing the required information is "deemed in compliance" (22757.12(c)(3)).” | exactEQ confidence: high | California SB 53 |
| METRShadow mapping METR | “Common Elements crosswalks lab frameworks to "the EU GPAI Code of Practice and California SB 53".” | closeCL confidence: medium | METR |
| Frontier Model ForumShadow mapping Frontier Model Forum, Risk Taxonomy and Thresholds | “Member synonyms: "Amazon 'Critical Capability Thresholds'; Google 'Critical Capability Levels'; Anthropic 'Capability Thresholds'; OpenAI 'Capability Thresholds'; Microsoft 'Capability Thresholds'" (s3.1).” | closeCL confidence: medium | Frontier Model Forum, Risk Taxonomy and Thresholds |
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
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.
- Anthropic
Explicit non-mapping: "We use this term in its plain meaning rather than adopting any specific statutory definition"; statutory requirements handled "in separate compliance frameworks" (§1 fn 1). Frontier Compliance Framework (SB 53) announced 19 Dec 2025; CASRAI has not retrieved that document or verified it against the primary text.
Anthropic Risk Report (August 2026) - Google DeepMind
FSF fn 1 cites UK DSIT 'Emerging processes', METR, Anthropic RSP and SB 53 compliance framework, OpenAI PF and FMF reports as informing it; the FSF 'does not itself say it is an SB 53 or EU Code of Practice compliance document'.
Google DeepMind Frontier Safety Framework v3.1 - Meta
"we note that there is a lack of consensus among industry and within regulatory frameworks as to how to define some of these terms and concepts." (Appendix I)
Meta Advanced AI Scaling Framework v2
Gap
The research found no legally operative mapping declaration in the corpus other than SB 53's declaration-of-intent record. NIKOLAI's mapping-declaration registry can copy its shape (declaring party, target instrument, date, revocation) while recording clearly that a NIKOLAI crosswalk entry is analysis, not a declaration by the mapped party.







