Choose an institution to see its records and dossier, or choose a topic.
Through year 2027 · all records, including scheduled dates 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2008 2005 1965 Show Organisations and infrastructure All types Organisation Person Document Concept Infrastructure Public body Reset filters
94 people, organisations and other records · 122 relationships · 34 claims about a valueEverything recorded up to the chosen year, whether or not still in effect · Undated records included
Claim and evidence Close ×
SB 53 requires a frontier developer to report any critical safety incident involving one or more of its frontier models to the Office of Emergency Services within 15 days of discovering it. Copy claim link
Copy claim reference
Machine-checked, not reviewed by an editor Stated in source Supported
Supporting evidence: primary · 1 source
Provision Required action · provision ID sb53-critical-safety-incident-report-15-days Informed Office of Emergency Services Subject version Chaptered (Stats. 2025, ch. 138) · Published 2025-09-29 · Effective 2026-01-01 Date 2025-09-29 · publication Scope and limits What the enacted text states, quoted from the chaptered expression. It is not evidence that the statute applies to any named developer, or of compliance, enforcement or effect. § 22757.13(c)(1) is expressly 'subject to paragraph (2)', the 24-hour imminent-risk disclosure (separate record). How the two duties relate is a question of legal interpretation and is not recorded here. Under § 22757.13(h)–(i), OES may adopt regulations designating federal laws, regulations or guidance documents whose incident-reporting standards are substantially equivalent to, or stricter than, this section's. A frontier developer that declares to OES its intent to comply through such a designated standard is deemed in compliance with § 22757.13 to the extent it meets that standard (separate record). This record does not establish that any designation or declaration exists. A developer that later discovers information about an incident may file an amended report (§ 22757.13(c)(3)). Reporting critical safety incidents involving foundation models that are not frontier models is encouraged, not required (§ 22757.13(c)(4)). Critical safety incident reports submitted to OES under § 22757.13 are exempt from the California Public Records Act (§ 22757.13(f)). Beginning 1 January 2027, and annually thereafter, OES must produce a report with anonymised, aggregated information about the critical safety incidents it has reviewed. It must transmit that report to the Legislature and the Governor (§ 22757.13(g)). No incident or report is recorded.
The evidence 02 primary source Supports the claim
SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025) ↗ California Legislature (California Legislative Information, Office of Legislative Counsel) · 2025-09-29
Archived copy, captured 2025-09-30: SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025) ↗
Copy source reference
Cite the original source Cite the original document, not Selekoa. Check these details against it.
Copy APA
Download BibTeX Download RIS Download CSL-JSON
Source excerpt “report any critical safety incident pertaining to one or more of its frontier models to the Office of Emergency Services within 15 days of discovering the critical safety incident.” Location in source SEC. 2, Bus. & Prof. Code § 22757.13(c)(1)
Machine-checked · 2026-10-04
Source details and check notes Authors California Legislature Version Chaptered version dated 09/29/25, inspected live 2026-10-04; quote also matched in the 2025-09-30 capture Canonical address Open the canonical source ↗ Accessed 2026-10-04 Language English (en) Archive copy Open archived copy, captured 2025-09-30: SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025) ↗ . Captured 1 day after the recorded publication date. An archive copy shows only what the archive retrieved on 2025-09-30. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-10-04.Attribution California Legislature, SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025). Reuse Official government text; no redistribution licence asserted. Selekoa practice: metadata, attributed paraphrases and short attributed quotations under the editorial policy (at most 50 words each; at most 400 quoted words per document across the dataset, and about 10% of a document under about 2,000 words). Documents are linked externally, not redistributed. Publisher terms that forbid quotation override this practice. Check notes Verbatim excerpt proposed by a research agent and checked by two independent fresh-context verifier agents and decided by a third adjudicating agent on 2026-10-04; re-matched mechanically by the integrator against a direct fetch of the cited expression. 29 words. The subject is 'a frontier developer shall', and the duty is 'Subject to paragraph (2)'. Human editorial review is pending. primary source Supports the claim
SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025) ↗ California Legislature (California Legislative Information, Office of Legislative Counsel) · 2025-09-29
Archived copy, captured 2025-09-30: SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025) ↗
Copy source reference
Cite the original source Cite the original document, not Selekoa. Check these details against it.
Copy APA
Download BibTeX Download RIS Download CSL-JSON
Paraphrase a 'critical safety incident' is any of the following. (1) Unauthorised access to, modification of or exfiltration of frontier-model weights that results in death or bodily injury. (2) Harm from a materialised catastrophic risk. (3) Loss of control of a frontier model causing death or bodily injury. (4) A frontier model using deceptive techniques against its developer to subvert controls or monitoring, outside an evaluation designed to elicit that behaviour, in a way that shows materially increased catastrophic risk.
Location in source SEC. 2, Bus. & Prof. Code § 22757.11(d)
Machine-checked · 2026-10-04
Source details and check notes Authors California Legislature Version Chaptered version dated 09/29/25, inspected live 2026-10-04; quote also matched in the 2025-09-30 capture Canonical address Open the canonical source ↗ Accessed 2026-10-04 Language English (en) Archive copy Open archived copy, captured 2025-09-30: SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025) ↗ . Captured 1 day after the recorded publication date. An archive copy shows only what the archive retrieved on 2025-09-30. It does not prove what the page said earlier, and it can differ from the copy checked on 2026-10-04.Attribution California Legislature, SB-53 Artificial intelligence models: large developers. (2025-2026) — bill text, chaptered version (Chapter 138, Statutes of 2025). Reuse Official government text; no redistribution licence asserted. Selekoa practice: metadata, attributed paraphrases and short attributed quotations under the editorial policy (at most 50 words each; at most 400 quoted words per document across the dataset, and about 10% of a document under about 2,000 words). Documents are linked externally, not redistributed. Publisher terms that forbid quotation override this practice. Check notes Editorial paraphrase proposed by a research agent and checked by two independent fresh-context verifier agents and decided by a third adjudicating agent on 2026-10-04. Paraphrased to stay within the quotation budget. Human editorial review is pending. Status and meaning Editorial status. Not reviewed by an editor . An exploratory record that no editor has accepted. This status does not say whether a person has read any linked passage. Each evidence record above shows how it was checked.
Relation. An exact framework edition states one provision: a capability threshold or risk level and its trigger, a required safeguard or action, a decision authority (who decides, recommends, can overrule or is informed), or a stated exception. The quoted text records what the edition says, not implementation, compliance or effectiveness. Provisions with the same key align across editions of one family.
Date. Provision as stated in the chaptered text published and approved on 2025-09-29; the added sections took effect on 2026-01-01. Text as chaptered on 2025-09-29. Effective 2026-01-01 according to the codified section's history note, 'Effective January 1, 2026' (https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC§ionNum=22757.13, checked 2026-10-04), which shows no amendment. The chaptered bill text itself states no effective date.
Record ID sb-critical-incident-15-days