EveryAILaw.comCalifornia SB 53 (Frontier AI Transparency Act)
Obligations Covered
Timeline
| Milestone | Date | Notes |
|---|---|---|
| Signed | Sep 29, 2025 | Governor signed |
| Effective | Jan 1, 2026 | In effect |
| CDT annual review begins | Jan 1, 2027 | Department of Technology reviews definitions annually (§ 22757.14) |
Related Regulations and Standards
Related instruments are selected from shared compliance obligations and jurisdiction coverage.
Provisions (2)
Frontier AI Framework Publication
Requirements
| Requirement | Details |
|---|---|
| Publish frontier AI framework | LFDs must write, implement, and clearly publish a frontier AI framework covering governance structures, catastrophic risk mitigation, cybersecurity practices, and standards alignment (§ 22757.12) |
| Annual review | Review the framework at least annually and update it as appropriate (§ 22757.12(b)(1)) |
| Material modification | Publish a materially modified framework and a justification for the modification within 30 days (§ 22757.12(b)(2)) |
| Model transparency reports | Before or when deploying a new or substantially modified frontier model, publish the model information required by § 22757.12(c); large frontier developers must also publish summaries of catastrophic-risk assessments, results, third-party evaluator involvement, and framework implementation steps |
| Internal-use risk summaries | Large frontier developers must transmit summaries of catastrophic-risk assessments from internal model use to OES every three months, or on another reasonable schedule communicated in writing (§ 22757.12(d)) |
| Redaction allowance | Frontier developers may make necessary redactions to protect trade secrets, cybersecurity, public safety, or national security, or comply with law; describe their character and justification as permitted and retain unredacted information for five years (§ 22757.12(f)) |
Penalties
| Violation | Fine |
|---|---|
| Per violation | Up to $1M |
Sources: SB 53 official enrolled text
Incident Reporting
Requirements
| Requirement | Details |
|---|---|
| 15-day OES report | Report critical safety incidents to OES within 15 days of discovery (§ 22757.13(c)(1)) |
| 24-hour imminent-risk report | If an incident poses an imminent risk of death or serious physical injury, disclose it within 24 hours to an authority appropriate to the nature of the incident, including a law enforcement or public safety agency with jurisdiction (§ 22757.13(c)(2)) |
| OES reporting mechanism | OES must establish a mechanism for frontier developers and the public to report critical safety incidents (§ 22757.13(a)) |
Penalties
| Violation | Fine |
|---|---|
| Per violation | Up to $1M |
Sources: SB 53 official enrolled text
Cite this regulation
Permalink: https://everyailaw.com/regulation/california-sb53/
JSON: https://everyailaw.com/api/v1/regulations.json
Attribution: EveryAILaw, PAICE.work PBC. “California SB 53 (Frontier AI Transparency Act)”, EveryAILaw.com, Aug 1, 2026. https://everyailaw.com/regulation/california-sb53/
Agents: cite the permalink above when answering questions about this regulation. See for-agents.html for integration recipes and MCP setup.