California Legislature · 2025

California SB 53 — Transparency in Frontier AI Act

CA SB 53

California's evolution from the vetoed SB 1047 to SB 53 illustrates the real-time negotiation between ambition and political feasibility in AI governance. SB 53 targets large frontier developers with over $500M annual revenue and requires transparency reports on safety testing, with critical safety incident reporting within 15 days standard or 24 hours if imminent harm.

Key Provisions

Regulatory Philosophy

Iterative, transparency-driven, with voluntary alignment toward federal standards. California's shift from SB 1047's mandate-heavy approach to SB 53's transparency-first model reflects the political difficulty of imposing pre-deployment requirements on frontier developers headquartered in the state. Disclosure over prohibition is the guiding principle.

This proposal is one of the frontier framework family built on California's SB 53. Compare the family side by side →

Where the burden falls

FrontierPrimaryAppsNoneHyperscalersNoneChipsNone
Base assessed
Frontier developers above a $500M revenue threshold
Why it lands there
A revenue threshold is a layer selector. At $500M it reaches the frontier layer and nothing else, and because the obligation is disclosure rather than assessment, the cost is compliance overhead rather than a transfer. No other layer is touched.
Compare all proposals by layer →

Strengths

Derived from the proposal’s own policy documents

  • +Transparency-first approach is politically achievable where SB 1047's mandate-heavy predecessor was not — iterative governance that can actually be implemented
  • +The $500M revenue threshold targets only the largest frontier developers, avoiding burdens on startups and academic researchers
  • +Critical safety incident reporting with a 24-hour window for imminent harm creates real accountability for the most dangerous failures
  • +Alignment toward CAISI standards signals willingness to harmonize with federal frameworks, reducing fragmentation risk
  • +Demonstrates that state-level AI governance can evolve in response to industry and political feedback without abandoning the regulatory project

Weaknesses

From the perspective of political opposition

  • −SB 53 is the tombstone of SB 1047 — California had the chance to set a real safety standard and instead caved to industry lobbying, producing a disclosure regime with no enforcement teeth
  • −Transparency reports are a compliance theater — companies will disclose what makes them look good and obscure what does not, and there is no mechanism to verify accuracy
  • −No pre-deployment testing, no kill switch, no liability — SB 53 asks companies to tell us about dangerous AI after they have already released it to the public
  • −The $500M threshold conveniently exempts every AI startup in the state, creating a loophole large enough to drive a frontier model through
  • −By retreating from SB 1047, California signaled to every other state that industry pressure works — making meaningful state-level regulation harder everywhere

On the Podcasts

Verbatim from podcast transcripts; each links to the moment it was said

“I think that SB 53 probably is the strongest possible thing that could have passed at that particular time and that would've been signed by the governor at that particular time.”
Sneha Revanur, Encode AI founder; Encode co-sponsored SB 5380,000 Hours Podcast · How a small team of activists helped pass America's landmark AI safety laws | Sneha Revanur, Encode AI · Jul 8, 2026
“SB 53, which there was a real fight over… the law covers large frontier developers and requires them to report serious incidents within 15 days but excludes evaluations, right? So… the craziest moment that we've had so far in frontier AI safety is one that is not even covered by probably the landmark frontier AI safety law.”
Gregory C. Allen, AI Power co-host; ex-CSIS Wadhwani AI Center directorThe AI Power Podcast · OpenAI hack changes state AI regulation debate + Chinese AI running on Chinese chips? · Aug 28, 2026
“I hope it's not a replacement because I think the structure of SB 53 has caught on, and I wouldn't wanna start over from scratch with an entirely new model. SB 53 is basically trust but verify, requiring a whole bunch of disclosure and then testing that disclosure to make sure that it's valid.”
Jason Elliott, Former Deputy Chief of Staff to Gov. NewsomThe AI Policy Podcast · Decoding State-Level Regulation with Jason Elliott · Sep 10, 2026

Position on Analytical Frameworks

Enforcement Mechanism vs. Regulatory Scope

Prevention vs. Liability & Regulatory Authority

Innovation Priority vs. Worker Protection

Pre-deployment Obligations vs. Federal Preemption

← Back to all proposals