SB 53 · 2025-26
Requires large AI developers to publish safety frameworks
Official subject Artificial intelligence models: large developers.
Became law Chapter 138, Statutes of 2025
Plain-language summary
Requires large developers of frontier AI models to publish a framework for managing catastrophic risks and send risk summaries to the Office of Emergency Services. The office must set up a way to report safety incidents. Protects employees who report dangers. Plans a public computing cluster called CalCompute. The Attorney General enforces civil penalties.
Official summary · Legislative Counsel's Digest
Describes the final version (Chaptered, Sept. 29, 2025).
Read the official summary (12 paragraphs)
(1)Existing law generally regulates artificial intelligence, including by requiring, on or before January 1, 2026, and before each time thereafter, that a generative artificial intelligence system or service, or a substantial modification to a generative artificial intelligence system or service, released on or after January 1, 2022, is made publicly available to Californians for use, the developer of the system or service to post on the developer’s internet website documentation regarding the data used by the developer to train the generative artificial intelligence system or service, as prescribed.
This bill would enact the Transparency in Frontier Artificial Intelligence Act (TFAIA) that would, among other things related to ensuring the safety of a foundation model, as defined, developed by a frontier developer, require a large frontier developer to write, implement, and clearly and conspicuously publish on its internet website a frontier AI framework that applies to the large frontier developer’s frontier models and describes how the large frontier developer approaches, among other things, incorporating national standards, international standards, and industry-consensus best practices into its frontier AI framework. The TFAIA would also require a large frontier developer to transmit to the Office of Emergency Services a summary of any assessment of catastrophic risk, as defined, resulting from internal use of its frontier models, as specified. The TFAIA would require the Office of Emergency Services to establish a mechanism to be used by a frontier developer or a member of the public to report, as prescribed, a critical safety incident, as defined, and would also require the Office of Emergency Services to establish a mechanism to be used by a large frontier developer to confidentially submit summaries of any assessments of the potential for catastrophic risk resulting from internal use of its frontier models, as prescribed.
The TFAIA would exempt from the California Public Records Act a report of a critical safety incident submitted to the Office of Emergency Services, a report of assessments of catastrophic risk from internet use, and a covered employee report made pursuant to the whistleblower protections described below.
The TFAIA would impose a civil penalty for noncompliance with the TFAIA to be enforced by the Attorney General, as prescribed.
(2)Existing law establishes the Department of Technology within the Government Operations Agency. Existing law requires the department to conduct, in coordination with other interagency bodies as it deems appropriate, a comprehensive inventory of all high-risk automated decision systems that have been proposed for use, development, or procurement by, or are being used, developed, or procured by, any state agency.
This bill would establish within the Government Operations Agency a consortium required to develop a framework for the creation of a public cloud computing cluster to be known as “CalCompute” that advances the development and deployment of artificial intelligence that is safe, ethical, equitable, and sustainable by, among other things, fostering research and innovation that benefits the public, as prescribed. The bill would require the Government Operations Agency to, on or before January 1, 2027, submit a report from the consortium to the Legislature with that framework and would dissolve the consortium upon submission of that report. The bill would make those provisions operative only upon an appropriation in a budget act, or other measure, for its purposes.
(3)Existing law prohibits employers and their agents from making, adopting, or enforcing a rule, regulation, or policy preventing an employee from disclosing information to certain entities or from providing information to, or testifying before, any public body conducting an investigation, hearing, or inquiry if the employee has reasonable cause to believe that the information discloses a violation of a law, as specified, and prohibits retaliation against an employee for, among other things, exercising these rights.
This bill would, among other things related to protecting whistleblowers working with foundation models, prohibit a frontier developer from making, adopting, enforcing, or entering into a rule, regulation, policy, or contract that prevents a covered employee, as defined, from disclosing, or retaliates against a covered employee for disclosing, information to the Attorney General, a federal authority, a person with authority over the covered employee, or another covered employee who has authority to investigate, discover, or correct the reported issue, if the covered employee has reasonable cause to believe that the information discloses that the frontier developer’s activities pose a specific and substantial danger to the public health or safety resulting from a catastrophic risk or that the frontier developer has violated the TFAIA.
This bill would require a large frontier developer to provide a certain internal process through which a covered employee may anonymously disclose information to the large frontier developer if the covered employee believes in good faith that the information indicates that the large frontier developer’s activities present a specific and substantial danger to the public health or safety resulting from a catastrophic risk or that the large frontier developer violated the TFAIA. The bill would specify provisions particular to the enforcement of those whistleblower protections and would authorize attorney’s fees to a plaintiff who brings a successful action for a violation.
This bill would preempt any rule, regulation, code, ordinance, or other law adopted by a city, county, city and county, municipality, or local agency on or after January 1, 2025, specifically related to the regulation of frontier developers with respect to their management of catastrophic risk.
Existing constitutional provisions require that a statute that limits the right of access to the meetings of public bodies or the writings of public officials and agencies be adopted with findings demonstrating the interest protected by the limitation and the need for protecting that interest.
This bill would make legislative findings to that effect.
Official title
An act to add Chapter 25.1 (commencing with Section 22757.10) to Division 8 of the Business and Professions Code, to add Section 11546.8 to the Government Code, and to add Chapter 5.1 (commencing with Section 1107) to Part 3 of Division 2 of the Labor Code, relating to artificial intelligence.
Timeline
- Jan. 7, 2025 Introduced
- May 28, 2025 Passed Senate 37 yes, 0 no
- Sept. 12, 2025 Passed Assembly 59 yes, 7 no
- Sept. 23, 2025 Enrolled and sent to the Governor
- Sept. 29, 2025 Signed by the Governor
- Sept. 29, 2025 Chaptered (became law)
Full official history (42 actions)
- Jan. 7, 2025 Introduced: Introduced. Read first time. To Com. on RLS. for assignment. To print.
- Jan. 8, 2025 From printer. May be acted upon on or after February 7.
- Jan. 29, 2025 Referred to Com. on RLS.
- Feb. 27, 2025 From committee with author's amendments. Read second time and amended. Re-referred to Com. on RLS.
- March 12, 2025 Re-referred to Coms. on G.O. and JUD.
- March 17, 2025 Set for hearing March 25.
- March 26, 2025 From committee: Do pass as amended and re-refer to Com. on JUD. (Ayes 13. Noes 0. Page 530.) (March 25).
- March 27, 2025 Read second time and amended. Re-referred to Com. on JUD.
- April 1, 2025 Set for hearing April 8.
- April 9, 2025 From committee: Do pass and re-refer to Com. on APPR. with recommendation: To consent calendar. (Ayes 13. Noes 0. Page 705.) (April 8). Re-referred to Com. on APPR.
- April 10, 2025 Set for hearing April 21.
- April 21, 2025 April 21 hearing: Placed on APPR. suspense file.
- May 16, 2025 Set for hearing May 23.
- May 23, 2025 From committee: Do pass as amended. (Ayes 6. Noes 0. Page 1189.) (May 23).
- May 23, 2025 Read second time and amended. Ordered to second reading.
- May 27, 2025 Read second time. Ordered to third reading.
- May 28, 2025 Passed Senate: Read third time. Passed. (Ayes 37. Noes 0. Page 1281.) Ordered to the Assembly.
- May 28, 2025 In Assembly. Read first time. Held at Desk.
- June 5, 2025 Referred to Coms. on P. & C.P. and JUD.
- June 12, 2025 Re-referred to Coms. on JUD. and P. & C.P. pursuant to Assembly Rule 96.
- July 2, 2025 From committee: Do pass and re-refer to Com. on P. & C.P. (Ayes 12. Noes 0.) (July 1). Re-referred to Com. on P. & C.P.
- July 8, 2025 From committee with author's amendments. Read second time and amended. Re-referred to Com. on P. & C.P.
- July 16, 2025 From committee: Do pass as amended and re-refer to Com. on APPR. (Ayes 9. Noes 0.) (July 16).
- July 17, 2025 Read second time and amended. Re-referred to Com. on APPR.
- Aug. 20, 2025 August 20 set for first hearing. Placed on APPR. suspense file.
- Aug. 29, 2025 From committee: Do pass as amended. (Ayes 11. Noes 1.) (August 29).
- Sept. 2, 2025 Read second time and amended. Ordered to second reading.
- Sept. 3, 2025 Read second time. Ordered to third reading.
- Sept. 5, 2025 Assembly Rule 69(b)(1) suspended.
- Sept. 5, 2025 Read third time and amended.
- Sept. 5, 2025 Ordered to third reading.
- Sept. 8, 2025 Re-referred to Com. on P. & C.P. pursuant to Assembly Rule 77.2.
- Sept. 9, 2025 Joint Rule 62(a) suspended.
- Sept. 11, 2025 From committee: Do pass. (Ayes 12. Noes 1.) (September 11).
- Sept. 12, 2025 Read second time. Ordered to third reading.
- Sept. 12, 2025 Assembly Rule 63 suspended.
- Sept. 12, 2025 Passed Assembly: Read third time. Passed. (Ayes 59. Noes 7. Page 3432.) Ordered to the Senate.
- Sept. 13, 2025 In Senate. Concurrence in Assembly amendments pending.
- Sept. 13, 2025 Assembly amendments concurred in. (Ayes 29. Noes 8. Page 3039.) Ordered to engrossing and enrolling.
- Sept. 23, 2025 Enrolled and sent to the Governor: Enrolled and presented to the Governor at 2 p.m.
- Sept. 29, 2025 Signed by the Governor: Approved by the Governor.
- Sept. 29, 2025 Chaptered (became law): Chaptered by Secretary of State. Chapter 138, Statutes of 2025.