Glossary · term

California SB 53 / TFAIA

California SB 53 is the 2025 state law whose enacted provisions include the Transparency in Frontier Artificial Intelligence Act, or TFAIA. It creates transparency and risk-governance duties for developers meeting the statute's definitions of frontier developer and, for some duties, large frontier developer. Those duties include public disclosures about covered frontier models, a published frontier AI framework for large frontier developers, defined reporting channels for critical safety incidents and internal catastrophic-risk assessments, and specified whistleblower protections.

Regulation2025-01-07Wave 2 · 2024Maturity: 5/5

Origin and context

SB 53 began as a California Senate bill on 7 January 2025 and was amended repeatedly before passage. The final act was approved and chaptered on 29 September 2025 as Chapter 138 of the Statutes of 2025. Its structure reflects a different regulatory approach from the vetoed SB 1047: the enacted law centers on transparency, developer frameworks, reporting, and protected disclosures rather than reproducing every duty or liability mechanism proposed in the earlier bill. Independent legal analysis published after enactment confirms the final scope and its 1 January 2026 effective date.

Sources: s1, s2, s3

Why it matters

TFAIA turns several frontier-model governance practices into California legal obligations. It distinguishes all frontier developers from large frontier developers, ties coverage to statutory compute and revenue definitions, and gives public agencies and the Attorney General roles in receiving information and enforcing noncompliance. For governance teams, that makes model classification, disclosure ownership, incident escalation, internal-use assessment, and employee-reporting processes operational questions rather than optional policy language. It also matters as a concrete example of jurisdiction-specific frontier AI regulation, but it should not be treated as a universal template for other states or countries.

Sources: s1, s3

Example

A developer considering a new frontier-model deployment would first determine whether the model and organization meet the law's defined thresholds. The applicable duties can then differ: a frontier developer may have transparency-reporting and critical-safety-incident obligations, while a large frontier developer also has framework and internal catastrophic-risk assessment duties. If an incident occurs, the team must apply the statute's definition and timing rules, including the shorter deadline for an imminent risk of death or serious physical injury. This is a legal classification exercise, not a generic safety checklist.

Sources: s1, s3

How it differs

AI incident reporting

Critical-safety-incident reporting is one component of SB 53. TFAIA is the wider statute and also covers frontier AI frameworks, transparency reports, internal-use assessments, whistleblower protections, enforcement, and CalCompute-related provisions. The two terms are related, not synonyms.

California SB 1047

SB 1047 was a separate 2024 bill that passed the Legislature but was vetoed. SB 53 was enacted in 2025 with a different title, coverage design, and set of duties; it is not merely SB 1047 renamed or revived wholesale.

Maturity and evidence

Maturity is rated 5 because SB 53 was approved, chaptered, and took effect as California law. The rating describes legal status, not evidence that every implementation question is settled or that the regime has demonstrated effectiveness. Definitions can be updated through mechanisms specified in the act, agency processes still shape operation, and the law's duties apply only when its actor, model, activity, and jurisdictional conditions are met.

Sources: s1, s2, s3

Limits and open questions

This entry is an educational overview, not legal advice. The chaptered text must be checked for the current definition, exception, deadline, confidentiality rule, enforcement provision, and effective date relevant to a particular organization. Not every foundation model is a frontier model, not every frontier developer is a large frontier developer, and not every adverse event is a critical safety incident. Public summaries can omit amendments or qualifications. The page therefore avoids converting selected thresholds or reporting deadlines into a universal compliance rule.

Sources: s1, s3

Related terms

References

Last updated: 2026-09-05

In the Skills Atlas

This term is also covered in the Skills Atlas as ai risk management skill.

In the Skills Atlas

This term is also covered in the Skills Atlas as eu ai act compliance skill.