The duty date already passed. California SB 53, chaptered as Chapter 138, took effect 1 January 2026. Large frontier developers owe a public framework page. Deploying a new or substantially modified frontier model also owes a transparency report. This is not SB 942.

The news

The Legislative Counsel's Digest for SB 53 (Wiener) says the bill enacts the Transparency in Frontier Artificial Intelligence Act (TFAIA). It requires a large frontier developer to write, implement, and clearly and conspicuously publish on its internet website a frontier AI framework that applies to that developer's frontier models and describes how the developer approaches, among other things, incorporating national standards, international standards, and industry-consensus best practices into the framework. The digest also requires a large frontier developer to transmit to the Office of Emergency Services a summary of any assessment of catastrophic risk resulting from internal use of its frontier models, as specified.

Section 22757.12(a) requires a large frontier developer to write, implement, comply with, and clearly and conspicuously publish that framework. Section 22757.12(c)(1) requires that before, or concurrently with, deploying a new frontier model or a substantially modified version of an existing frontier model, a frontier developer publish a transparency report that includes, among other listed items, the developer's website, a mechanism for a natural person to communicate with the developer, the release date, languages supported, and output modalities.

Section 22757.12(e) says a frontier developer shall not make a materially false or misleading statement about catastrophic risk from its frontier models or its management of catastrophic risk, and a large frontier developer shall not make a materially false or misleading statement about implementation of or compliance with its frontier AI framework.

The code annotation on 22757.12 states: "Added by Stats. 2025, Ch. 138, Sec. 2. (SB 53) Effective January 1, 2026."

Who is bound

The California Legislature and Governor shipped the statute. Bound are frontier developers and large frontier developers as those terms are defined in the chapter. The Office of Emergency Services is the recipient of specified catastrophic-risk summaries. The Attorney General's enforcement mechanics sit in the chapter text beyond the digest. Read the penalty schedule in the chaptered PDF. Don't infer it here.

What's new

Relative to the vetoed 2024 SB 1047 fight, this is the statute that actually took effect on 1 January 2026: publication duties and a false-statement bar, not a compute-licensing bureau. It is separate from California's SB 942 AI Transparency Act, which AB 853 delayed to 2 August 2026.

What it does not settle

Date: effective 1 January 2026. Region: California. Price: none in the digest. Hardware: none. Data: framework contents and transparency-report fields listed in 22757.12. License: not a software license. The exact statutory definition of "large frontier developer" and any FLOPS or compute cutoff is in the chaptered definitions section. This Dispatch does not rest on secondary restatements of that cutoff. UNKNOWN here pending a line cite from that definitions section in a follow-up.

What to do now

Counsel at labs that ship frontier models used in California should map the public framework URL and the last transparency report against 22757.12(a) and (c). Communications staff should treat catastrophic-risk claims as 22757.12(e) statements.

Whether any named lab's current website meets 22757.12 is UNKNOWN.