State Laws Affecting Frontier US AI Companies
Bill page — New York

RAISE Act · Responsible AI Safety and Education Act

Enacted — effective 1 Jan 2027
A plain-language summary laid over the statute. Every row below opens the text it comes from; the margin marks where New York departs from the California baseline.
Version read
Enacted text
Citation
N.Y. Gen. Bus. Law art. 44-B, §§ 1420-1429 (S8828, ch. 96 of 2026)
Effective
2027-01-01
Last verified
1 August 2026
Baseline
Cal. SB 53

High-level summary

Ordered by novelty · open a row for detail · the cite jumps to the text
An SB 53 copy, plus a DFS registration regime, plus a 72-hour incident clock, minus whistleblower protections.
New — no CA analogue
DFS registration: no disclosure statement on file, no developing or deploying a frontier model in New York.
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1428(1)-(2)
New — no CA analogue
Large frontier developers pay pro rata assessments to fund the regulator.
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1428(4)
New — no CA analogue
$1,000 per day for operating unregistered, filing false information, or not paying assessments.
Binds you if
Binds any person developing, deploying, or operating a large frontier model in part in New York without a current disclosure on file
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1428(5)
New — no CA analogue
DFS publishes the list of large frontier developers who have registered.
Binds you if
Binds the office, not developers
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1428(6)
New — no CA analogue
Standing DFS rulemaking authority, including power to add reporting and publication requirements.
Binds you if
Binds the office; reaches every frontier developer the article covers once exercised
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1429
Tightens CA
Quarterly internal-use catastrophic-risk summaries to the office, on a schedule the office must agree to.
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1422(2)(a)
Tightens CA
72-hour critical safety incident reporting to the DFS office.
Binds you if
Binds you if you are any frontier developer — >10^26-operation model — operating in whole or in part in New York state (§§ 1420(8)-(9), 1425)
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1422(3)(a)
Tightens CA
Annual public incident report from the regulator, with recommended statutory updates.
Binds you if
Binds the office, not developers; first report due January 1, 2028
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1422(7)
Tightens CA
Federal-equivalence safe harbor, but copies of the federal reports still go to the office.
Binds you if
Binds you if you are any frontier developer — >10^26-operation model — operating in whole or in part in New York state (§§ 1420(8)-(9), 1425)
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1422(9)-(10)
Tightens CA
AG civil penalties: up to $1M first violation, up to $3M per subsequent violation.
Binds you if
Reaches only large frontier developers, and only the four listed procedural failures
Effective
2027-01-01
N.Y. Gen. Bus. Law § 1427(1)
Matches CA
8 provisions track the California baseline.
N.Y. Gen. Bus. Law § 1420(3) +7 more
↑ Summary

The Act

Enacted text, verbatim · quoted in statute order
N.Y. Gen. Bus. Law § 1420(3)
Matches CA
Compared →
Catastrophic risk: >50 deaths or >$1B in property damage, from CBRN, autonomous crime or cyberattack, or loss of control
3. (a) "Catastrophic risk" means a foreseeable and material risk that a frontier developer's [anyone who has trained, or started training, a model above 10^26 operations (§ 1420(8)-(9))] development, storage, use, or deployment of a frontier model will materially contribute to the death of, or serious injury to, more than fifty people or more than one billion dollars in damage to, or loss of, property arising from a single incident involving a frontier model doing any of the following: (i) providing expert-level assistance in the creation or release of a chemical, biological, radiological, or nuclear weapon; (ii) engaging in conduct with no meaningful human oversight, intervention, or supervision that is either a cyberattack or, if the conduct had been committed by a human, would constitute the crime of murder, assault, extortion, or theft, including theft by false pretense; or (iii) evading the control of its frontier developer or user. (b) "Catastrophic risk" does not include a foreseeable and material risk from any of the following: (i) information that a frontier model outputs if the information is otherwise publicly accessible in a substantially similar form from a source other than a foundation model; (ii) lawful activity of the federal government; or (iii) harm caused by a frontier model in combination with other software if the frontier model did not materially contribute to the harm.
Effective
2027-01-01
Binds you if
Defines the harm every other duty in the article is keyed to
Goes to
n/a — definitional
Duty
mandatory
Category
thresholds-scoping
N.Y. Gen. Bus. Law § 1420(9)-(10)
Matches CA
Compared →
10^26 operations, $500M revenue — California's thresholds, adopted verbatim
9. (a) "Frontier model" means a foundation model that was trained using a quantity of computing power greater than 10^26 integer or floating-point operations. (b) The quantity of computing power described in paragraph (a) of this subdivision shall include computing for the original training run and for any subsequent fine-tuning, reinforcement learning, or other material modifications the developer applies to a preceding foundation model. 10. "Large frontier developer" means a frontier developer that together with its affiliates collectively had annual gross revenues in excess of five hundred million dollars in the preceding calendar year.
Effective
2027-01-01
Binds you if
Defines who the article covers at all
Goes to
n/a — definitional
Duty
mandatory
Category
thresholds-scoping
N.Y. Gen. Bus. Law § 1421(1)
Matches CA
Compared →
Written, published, followed frontier AI framework on the SB 53 ten-topic template
§ 1421. Transparency requirements. 1. A large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] shall write, implement, comply with, 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 in detail how the large frontier developer handles all of the following: (a) incorporating national standards, international standards, and industry consensus best practices into its frontier AI framework; (b) defining and assessing thresholds used by the large frontier developer to identify and assess whether a frontier model has capabilities that could pose a catastrophic risk, [foreseeable, material risk of >50 deaths or serious injuries, or >$1B in property damage, from one incident (§ 1420(3))] which may include multiple-tiered thresholds; (c) applying mitigations to address the potential for catastrophic risks based on the results of assessments undertaken pursuant to paragraph (b) of this subdivision; (d) reviewing assessments and adequacy of mitigations as part of the decision to deploy a frontier model or use it extensively internally; (e) using third parties to assess the potential for catastrophic risks and the effectiveness of mitigations of catastrophic risks; (f) revisiting and updating the frontier AI framework, including any criteria that trigger updates and how the large frontier developer determines when its frontier models are substantially modified enough to require disclosures pursuant to subdivision three of this section; (g) cybersecurity practices to secure unreleased model weights from unauthorized modification or transfer by internal or external parties; (h) identifying and responding to critical safety incidents; (i) instituting internal governance practices to ensure implementation of these processes; and (j) assessing and managing catastrophic risk resulting from the internal use of its frontier models, including risks resulting from a frontier model circumventing oversight mechanisms.
Effective
2027-01-01
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Goes to
No filing — published on the developer's own website, so the public receives it
Duty
mandatory
Category
frontier-ai-framework
N.Y. Gen. Bus. Law § 1421(1)(e)
Matches CA
Compared →
Third-party assessment: describe your use of it — no audit required
(e) using third parties to assess the potential for catastrophic risks and the effectiveness of mitigations of catastrophic risks;
Effective
2027-01-01
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Goes to
Published on the developer's website as part of the framework; no auditor, no regulator
Duty
mandatory
Category
independent-verification
N.Y. Gen. Bus. Law § 1421(3)
Matches CA
Compared →
Transparency report at deployment, with catastrophic-risk assessment summaries for large developers
3. (a) Before, or concurrently with, deploying a new frontier model or a substantially modified version of an existing frontier model, a frontier developer [anyone who has trained, or started training, a model above 10^26 operations (§ 1420(8)-(9))] shall clearly and conspicuously publish on its internet website a transparency report containing all of the following: (i) the internet website of the frontier developer; (ii) a mechanism that enables a natural person to communicate with the frontier developer; (iii) the release date of the frontier model; (iv) the languages supported by the frontier model; (v) the modalities of output supported by the frontier model; (vi) the intended uses of the frontier model; and (vii) any generally applicable restrictions or conditions on uses of the frontier model. (b) Before, or concurrently with, deploying a new frontier model or a substantially modified version of an existing frontier model, a large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] shall include in the transparency report required by paragraph (a) of this subdivision, summaries of all of the following: (i) assessments of catastrophic risks from the frontier model conducted pursuant to the large frontier developer's frontier AI framework; (ii) the results of the assessments under subparagraph (i) of this paragraph; (iii) the extent to which third-party evaluators were involved; and (iv) other steps taken to fulfill the requirements of the frontier AI framework with respect to the frontier model. (c) A frontier developer that publishes the information described in paragraph (a) or (b) of this subdivision as part of a larger document, including a system card or model card, shall be deemed in compliance with the applicable paragraph.
Effective
2027-01-01
Binds you if
(a) binds any frontier developer deploying a new or substantially modified frontier model in New York; (b) adds the risk-assessment summaries only for large frontier developers
Goes to
Published on the developer's own website — public, not filed with the office
Duty
mandatory
Category
transparency-reports
N.Y. Gen. Bus. Law § 1421(4)
Matches CA
Compared →
No materially false or misleading statements about catastrophic risk or framework compliance
4. (a) (i) A frontier developer [anyone who has trained, or started training, a model above 10^26 operations (§ 1420(8)-(9))] shall not make a materially false or misleading statement about catastrophic risk [foreseeable, material risk of >50 deaths or serious injuries, or >$1B in property damage, from one incident (§ 1420(3))] from its frontier models or its management of catastrophic risk. (ii) A large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] shall not make a materially false or misleading statement about its implementation of, or compliance with, its frontier AI framework. (b) This subdivision shall not apply to a statement that was made in good faith and was reasonable under the circumstances.
Effective
2027-01-01
Binds you if
(a)(i) binds any frontier developer; (a)(ii) binds only large frontier developers
Goes to
n/a — a prohibition; the AG enforces it under § 1427(1)
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1422(2)(a)
Tightens CA
Compared →
Quarterly internal-use catastrophic-risk summaries to the office, on a schedule the office must agree to
2. (a) A large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] shall transmit to the office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] a summary of any assessment of catastrophic risk [foreseeable, material risk of >50 deaths or serious injuries, or >$1B in property damage, from one incident (§ 1420(3))] resulting from internal use of its frontier models every three months or pursuant to another reasonable schedule requested by the large frontier developer, communicated in writing to the office with written updates, as appropriate, and agreed upon by the office. The office shall 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.
Effective
2027-01-01
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Goes to
the office, confidentially; exempt from FOIL disclosure under § 1422(6)
Duty
mandatory
Category
internal-use-risk
N.Y. Gen. Bus. Law § 1422(3)(a)
Tightens CA
Compared →
72-hour critical safety incident reporting to the DFS office
3. (a) Subject to paragraph (b) of this subdivision, a frontier developer [anyone who has trained, or started training, a model above 10^26 operations (§ 1420(8)-(9))] shall report any critical safety incident [weight theft causing death or injury, realized catastrophic risk, loss of control causing death or injury, or a model deceiving its developer to subvert controls (§ 1420(4))] pertaining to one or more of its frontier models to the office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] within seventy-two hours from a determination that a critical safety incident has occurred or within seventy-two hours of the frontier developer learning facts sufficient to establish a reasonable belief that a critical safety incident has occurred.
Effective
2027-01-01
Binds you if
Binds you if you are any frontier developer — >10^26-operation model — operating in whole or in part in New York state (§§ 1420(8)-(9), 1425)
Goes to
the office (within DFS); the report is exempt from FOIL disclosure under § 1422(6)
Duty
mandatory
Category
incident-reporting
N.Y. Gen. Bus. Law § 1422(3)(b)
Matches CA
Compared →
24-hour disclosure to an authority with jurisdiction when death or serious injury is imminent
(b) If a frontier developer [anyone who has trained, or started training, a model above 10^26 operations (§ 1420(8)-(9))] discovers that a critical safety incident [weight theft causing death or injury, realized catastrophic risk, loss of control causing death or injury, or a model deceiving its developer to subvert controls (§ 1420(4))] poses an imminent risk of death or serious physical injury, the frontier developer shall disclose that incident within twenty-four hours to an authority, including any law enforcement agency or public safety agency with jurisdiction, that is appropriate based on the nature of that incident and as required by law.
Effective
2027-01-01
Binds you if
Binds you if you are any frontier developer — >10^26-operation model — operating in whole or in part in New York state (§§ 1420(8)-(9), 1425)
Goes to
NOT the office — 'an authority, including any law enforcement agency or public safety agency with jurisdiction'; not public
Duty
mandatory
Category
incident-reporting
N.Y. Gen. Bus. Law § 1422(7)
Tightens CA
Compared →
Annual public incident report from the regulator, with recommended statutory updates
7. (a) Beginning January first, two thousand twenty-eight, and annually thereafter, the office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] shall produce a report, that includes the following: (i) anonymized and aggregated information about critical safety incidents that have been reviewed by the office since the preceding report; (ii) any information that the office deems relevant to frontier model safety; (iii) recommended updates to this article, if any; and (iv) any developments relevant to the purposes of this article. (b) The office shall not include information in a report pursuant to this subdivision that would compromise the trade secrets or cybersecurity of a frontier developer, public safety, or the national security of the United States or that would be prohibited by any federal or state law. (c) The office shall transmit a report pursuant to this subdivision to the governor, the temporary president and minority leader of the senate, the speaker and minority leader of the assembly, the chair and ranking member of the senate committee on internet and technology, and the chair and ranking member of the assembly committee on science and technology.
Effective
2027-01-01
Binds you if
Binds the office, not developers; first report due January 1, 2028
Goes to
the Governor, both chambers' leaders, and the internet-and-technology and science-and-technology committee chairs and ranking members
Duty
mandatory
Category
incident-reporting
N.Y. Gen. Bus. Law § 1422(9)-(10)
Tightens CA
Compared →
Federal-equivalence safe harbor, but copies of the federal reports still go to the office
9. (a) A frontier developer [anyone who has trained, or started training, a model above 10^26 operations (§ 1420(8)-(9))] that intends to comply with subdivision three of this section by complying with the requirements of, or meeting the standards stated by, a federal law, regulation, or guidance document designated pursuant to subdivision eight of this section shall declare its intent to do so to the office. [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] (b) After a frontier developer has declared its intent pursuant to paragraph (a) of this subdivision, the following shall apply: (i) the frontier developer shall be deemed in compliance with subdivision three of this section to the extent that the frontier developer meets the standards of, or complies with the requirements imposed or stated by, the designated federal law, regulation, or guidance document until the frontier developer declares the revocation of that intent to the office or the office revokes a relevant regulation pursuant to subdivision ten of this section; (ii) the failure by a frontier developer to meet the standards of, or comply with the requirements stated by, the federal law, regulation, or guidance document designated pursuant to subdivision eight of this section shall constitute a violation of this article; and (iii) frontier developers who comply with subdivision three of this section by meeting such federal standards shall send copies of any critical safety incident [weight theft causing death or injury, realized catastrophic risk, loss of control causing death or injury, or a model deceiving its developer to subvert controls (§ 1420(4))] reports required by such federal standards to the office concurrently with sending them to federal authorities. 10. The office shall revoke a regulation adopted under subdivision eight of this section if the requirements of subdivision eight of this section are no longer met.
Effective
2027-01-01
Binds you if
Binds you if you are any frontier developer — >10^26-operation model — operating in whole or in part in New York state (§§ 1420(8)-(9), 1425)
Goes to
the office, concurrently with the federal authority
Duty
rulemaking
Category
incident-reporting
N.Y. Gen. Bus. Law § 1427(1)
Tightens CA
Compared →
AG civil penalties: up to $1M first violation, up to $3M per subsequent violation
§ 1427. Violations. 1. The attorney general may bring a civil action to recover a civil penalty in an amount not to exceed one million dollars for a first violation and in an amount not to exceed three million dollars per subsequent violation, determined based on the severity of the violation where a large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] fails to publish or transmit a compliant document required to be published or transmitted under this article, makes a statement in violation of subdivision four of section fourteen hundred twenty-one of this article, fails to report an incident as required by section fourteen hundred twenty-two of this article, or fails to comply with its own frontier AI framework.
Effective
2027-01-01
Binds you if
Reaches only large frontier developers, and only the four listed procedural failures
Goes to
the New York Attorney General, by civil action
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1427(2)-(3)
Matches CA
Compared →
No private right of action; third-party causation defense preserved
2. Nothing in this article shall be construed to establish, authorize or create a private right of action associated with violations of this article. 3. Nothing in this article shall be construed to prevent a large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] from asserting that another person, entity, or factor, may be responsible for any alleged harm, injury or damage resulting from a catastrophic risk or critical safety incident.
Effective
2027-01-01
Binds you if
Applies to anyone who might otherwise sue under the article
Goes to
n/a — a bar on suits
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1428(1)-(2)
New — no CA analogue
No CA analogue
Compared →
DFS registration: no disclosure statement on file, no developing or deploying a frontier model in New York
§ 1428. Large frontier developer disclosure. 1. Except as otherwise provided in this section, no large frontier developer [a frontier developer whose group had more than $500 million in gross revenue last year (§ 1420(10))] may develop, deploy, or operate a frontier model, in whole or in part in New York state, without having a current disclosure statement filed with the office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] and paying the required share. 2. The disclosure statement shall be filed in the form and the manner prescribed by the office and shall contain all the information required by the office. It shall be renewed every two years, whenever ownership of the frontier model is transferred or whenever there is a material change to the information reported in the previously filed disclosure statement, whichever occurs earlier.
Effective
2027-01-01
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Goes to
the office (DFS); the fact of filing is published under § 1428(6), the contact details are not
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1428(4)
New — no CA analogue
No CA analogue
Source →
Large frontier developers pay pro rata assessments to fund the regulator
4. Large frontier developers shall be assessed in pro rata shares by the department [the New York State Department of Financial Services (§ 1420(12))] to defray the operating expenses, including all direct and indirect costs, of administering the obligations imposed by this article.
Effective
2027-01-01
Binds you if
Binds you if you are a large frontier developer — >10^26-operation model plus >$500M group revenue — operating in whole or in part in New York state (§§ 1420(9)-(10), 1425)
Goes to
the department (DFS), which assesses the shares
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1428(5)
New — no CA analogue
No CA analogue
Compared →
$1,000 per day for operating unregistered, filing false information, or not paying assessments
5. If any person develops, deploys, or operates a large frontier model in part in New York state without a current disclosure filed with the office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] as required by this section, submits false information in its disclosure or fails to timely pay any assessment required by this article, in addition to any other penalty or liability that may be imposed under this article, the office may, after notice and hearing, levy civil penalties, fees, and costs as follows: (a) a civil penalty of one thousand dollars for each day the entity fails to file a disclosure as required by this section or fails to correct false information; and (b) an amount equal to the assessments owed.
Effective
2027-01-01
Binds you if
Binds any person developing, deploying, or operating a large frontier model in part in New York without a current disclosure on file
Goes to
the office (DFS), after notice and hearing — an administrative track, no court and no AG required
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1428(6)
New — no CA analogue
No CA analogue
Compared →
DFS publishes the list of large frontier developers who have registered
6. The office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] shall maintain and publish a list of large frontier developers who have filed disclosure statements, however such publication shall not include the contact information set forth in paragraph (d) of subdivision three of this section.
Effective
2027-01-01
Binds you if
Binds the office, not developers
Goes to
the public
Duty
mandatory
Category
enforcement
N.Y. Gen. Bus. Law § 1429
New — no CA analogue
No CA analogue
Compared →
Standing DFS rulemaking authority, including power to add reporting and publication requirements
§ 1429. Rulemaking authority. The office is hereby authorized to adopt rules and regulations to implement the provisions of this article as needed. To the extent the office [an office within the New York State Department of Financial Services, reporting to the Superintendent of Financial Services (§ 1420(16))] determines that doing so will facilitate safety and transparency consistent with the underlying purpose of this article, the office may consider additional reporting or publication requirements for information to facilitate safety and transparency, including but not limited to, post-critical safety incident information, sharing plans and protocols, and the transmission of frontier AI frameworks to the office.
Effective
2027-01-01
Binds you if
Binds the office; reaches every frontier developer the article covers once exercised
Goes to
n/a — grant of authority to the office
Duty
rulemaking
Category
enforcement
Full text ↗

Every quotation above is machine-checked against the archived official text before this page is built. Passages of the act outside the frontier-model duties this site tracks are not quoted here — read the whole the act on nysenate.gov ↗.

CACompared with — N.Y. Gen. Bus. Law § 1420(3)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.11(c)·leginfo.legislature.ca.gov, official text ↗
(c) (1) “Catastrophic risk” means a foreseeable and material risk that a frontier developer’s development, storage, use, or deployment of a frontier model will materially contribute to the death of, or serious injury to, more than 50 people or more than one billion dollars ($1,000,000,000) in damage to, or loss of, property arising from a single incident involving a frontier model doing any of the following: (A) Providing expert-level assistance in the creation or release of a chemical, biological, radiological, or nuclear weapon. (B) Engaging in conduct with no meaningful human oversight, intervention, or supervision that is either a cyberattack or, if the conduct had been committed by a human, would constitute the crime of murder, assault, extortion, or theft, including theft by false pretense. (C) Evading the control of its frontier developer or user. (2) “Catastrophic risk” does not include a foreseeable and material risk from any of the following: (A) Information that a frontier model outputs if the information is otherwise publicly accessible in a substantially similar form from a source other than a foundation model. (B) Lawful activity of the federal government.

Continue on leginfo.legislature.ca.gov ↗

CACompared with — N.Y. Gen. Bus. Law § 1420(9)-(10)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.11(i)-(j)·leginfo.legislature.ca.gov, official text ↗
(i) (1) “Frontier model” means a foundation model that was trained using a quantity of computing power greater than 10^26 integer or floating-point operations. (2) The quantity of computing power described in paragraph (1) shall include computing for the original training run and for any subsequent fine-tuning, reinforcement learning, or other material modifications the developer applies to a preceding foundation model. (j) “Large frontier developer” means a frontier developer that together with its affiliates collectively had annual gross revenues in excess of five hundred million dollars ($500,000,000) in the preceding calendar year.
CACompared with — N.Y. Gen. Bus. Law § 1421(1)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.12(a)·leginfo.legislature.ca.gov, official text ↗
(a) A large frontier developer shall write, implement, comply with, 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 all of the following: (1) Incorporating national standards, international standards, and industry-consensus best practices into its frontier AI framework. (2) Defining and assessing thresholds used by the large frontier developer to identify and assess whether a frontier model has capabilities that could pose a catastrophic risk, which may include multiple-tiered thresholds. (3) Applying mitigations to address the potential for catastrophic risks based on the results of assessments undertaken pursuant to paragraph (2). (4) Reviewing assessments and adequacy of mitigations as part of the decision to deploy a frontier model or use it extensively internally. (5) Using third parties to assess the potential for catastrophic risks and the effectiveness of mitigations of catastrophic risks.

Continue on leginfo.legislature.ca.gov ↗

CACompared with — N.Y. Gen. Bus. Law § 1421(1)(e)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.12(a)(5)·leginfo.legislature.ca.gov, official text ↗
(5) Using third parties to assess the potential for catastrophic risks and the effectiveness of mitigations of catastrophic risks.
CACompared with — N.Y. Gen. Bus. Law § 1421(3)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.12(c)(1)-(3)·leginfo.legislature.ca.gov, official text ↗
(c) (1) Before, or concurrently with, deploying a new frontier model or a substantially modified version of an existing frontier model, a frontier developer shall clearly and conspicuously publish on its internet website a transparency report containing all of the following: (A) The internet website of the frontier developer. (B) A mechanism that enables a natural person to communicate with the frontier developer. (C) The release date of the frontier model. (D) The languages supported by the frontier model. (E) The modalities of output supported by the frontier model. (F) The intended uses of the frontier model. (G) Any generally applicable restrictions or conditions on uses of the frontier model. (2) Before, or concurrently with, deploying a new frontier model or a substantially modified version of an existing frontier model, a large frontier developer shall include in the transparency report required by paragraph (1) summaries of all of the following: (A) Assessments of catastrophic risks from the frontier model conducted pursuant to the large frontier developer’s frontier AI framework. (B) The results of those assessments.

Continue on leginfo.legislature.ca.gov ↗

CACompared with — N.Y. Gen. Bus. Law § 1421(4)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.12(e)·leginfo.legislature.ca.gov, official text ↗
(e) (1) (A) 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. (B) A large frontier developer shall not make a materially false or misleading statement about its implementation of, or compliance with, its frontier AI framework. (2) This subdivision does not apply to a statement that was made in good faith and was reasonable under the circumstances.
CACompared with — N.Y. Gen. Bus. Law § 1422(2)(a)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.12(d)·leginfo.legislature.ca.gov, official text ↗
(d) A large frontier developer shall transmit to the Office of Emergency Services a summary of any assessment of catastrophic risk resulting from internal use of its frontier models every three months or pursuant to another reasonable schedule specified by the large frontier developer and communicated in writing to the Office of Emergency Services with written updates, as appropriate.
CACompared with — N.Y. Gen. Bus. Law § 1422(3)(a)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.13(c)(1)·leginfo.legislature.ca.gov, official text ↗
(c) (1) Subject to paragraph (2), a frontier developer shall report any critical safety incident pertaining to one or more of its frontier models to the Office of Emergency Services within 15 days of discovering the critical safety incident.
CACompared with — N.Y. Gen. Bus. Law § 1422(3)(b)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.13(c)(2)·leginfo.legislature.ca.gov, official text ↗
(2) If a frontier developer discovers that a critical safety incident poses an imminent risk of death or serious physical injury, the frontier developer shall disclose that incident within 24 hours to an authority, including any law enforcement agency or public safety agency with jurisdiction, that is appropriate based on the nature of that incident and as required by law.
CACompared with — N.Y. Gen. Bus. Law § 1422(7)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.13(g)·leginfo.legislature.ca.gov, official text ↗
(g) (1) Beginning January 1, 2027, and annually thereafter, the Office of Emergency Services shall produce a report with anonymized and aggregated information about critical safety incidents that have been reviewed by the Office of Emergency Services since the preceding report. (2) The Office of Emergency Services shall not include information in a report pursuant to this subdivision that would compromise the trade secrets or cybersecurity of a frontier developer, public safety, or the national security of the United States or that would be prohibited by any federal or state law. (3) The Office of Emergency Services shall transmit a report pursuant to this subdivision to the Legislature, pursuant to Section 9795, and to the Governor.
CACompared with — N.Y. Gen. Bus. Law § 1422(9)-(10)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.13(i)-(j)·leginfo.legislature.ca.gov, official text ↗
(i) (1) A frontier developer that intends to comply with this section by complying with the requirements of, or meeting the standards stated by, a federal law, regulation, or guidance document designated pursuant to subdivision (h) shall declare its intent to do so to the Office of Emergency Services. (2) After a frontier developer has declared its intent pursuant to paragraph (1), both of the following apply: (A) The frontier developer shall be deemed in compliance with this section to the extent that the frontier developer meets the standards of, or complies with the requirements imposed or stated by, the designated federal law, regulation, or guidance document until the frontier developer declares the revocation of that intent to the Office of Emergency Services or the Office of Emergency Services revokes a relevant regulation pursuant to subdivision (j). (B) The failure by a frontier developer to meet the standards of, or comply with the requirements stated by, the federal law, regulation, or guidance document designated pursuant to subdivision (h) shall constitute a violation of this chapter.

Continue on leginfo.legislature.ca.gov ↗

CACompared with — N.Y. Gen. Bus. Law § 1427(1)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.15(a)-(b)·leginfo.legislature.ca.gov, official text ↗
(a) A large frontier developer that fails to publish or transmit a compliant document required to be published or transmitted under this chapter, makes a statement in violation of subdivision (e) of Section 22757.12, fails to report an incident as required by Section 22757.13, or fails to comply with its own frontier AI framework shall be subject to a civil penalty in an amount dependent upon the severity of the violation that does not exceed one million dollars ($1,000,000) per violation. (b) A civil penalty described in this section shall be recovered in a civil action brought only by the Attorney General.
CACompared with — N.Y. Gen. Bus. Law § 1427(2)-(3)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.15(b)·leginfo.legislature.ca.gov, official text ↗
(b) A civil penalty described in this section shall be recovered in a civil action brought only by the Attorney General.
CACompared with — N.Y. Gen. Bus. Law § 1428(1)-(2)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.12(d)·leginfo.legislature.ca.gov, official text ↗
(d) A large frontier developer shall transmit to the Office of Emergency Services a summary of any assessment of catastrophic risk resulting from internal use of its frontier models every three months or pursuant to another reasonable schedule specified by the large frontier developer and communicated in writing to the Office of Emergency Services with written updates, as appropriate.
NYSource text — N.Y. Gen. Bus. Law § 1428(4)
New York RAISE Act (S6953-B / A6453-B), as repealed and replaced by S8828
N.Y. Gen. Bus. Law § 1428(4)·nysenate.gov, official text ↗
4. Large frontier developers shall be assessed in pro rata shares by the department to defray the operating expenses, including all direct and indirect costs, of administering the obligations imposed by this article.
CACompared with — N.Y. Gen. Bus. Law § 1428(5)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.15(a)-(b)·leginfo.legislature.ca.gov, official text ↗
(a) A large frontier developer that fails to publish or transmit a compliant document required to be published or transmitted under this chapter, makes a statement in violation of subdivision (e) of Section 22757.12, fails to report an incident as required by Section 22757.13, or fails to comply with its own frontier AI framework shall be subject to a civil penalty in an amount dependent upon the severity of the violation that does not exceed one million dollars ($1,000,000) per violation. (b) A civil penalty described in this section shall be recovered in a civil action brought only by the Attorney General.
CACompared with — N.Y. Gen. Bus. Law § 1428(6)
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.13(g)·leginfo.legislature.ca.gov, official text ↗
(g) (1) Beginning January 1, 2027, and annually thereafter, the Office of Emergency Services shall produce a report with anonymized and aggregated information about critical safety incidents that have been reviewed by the Office of Emergency Services since the preceding report. (2) The Office of Emergency Services shall not include information in a report pursuant to this subdivision that would compromise the trade secrets or cybersecurity of a frontier developer, public safety, or the national security of the United States or that would be prohibited by any federal or state law. (3) The Office of Emergency Services shall transmit a report pursuant to this subdivision to the Legislature, pursuant to Section 9795, and to the Governor.
CACompared with — N.Y. Gen. Bus. Law § 1429
Cal. SB 53
Cal. Bus. & Prof. Code § 22757.13(h)·leginfo.legislature.ca.gov, official text ↗
(h) The Office of Emergency Services may adopt regulations designating one or more federal laws, regulations, or guidance documents that meet all of the following conditions for the purposes of subdivision (i): (1) (A) The law, regulation, or guidance document imposes or states standards or requirements for critical safety incident reporting that are substantially equivalent to, or stricter than, those required by this section. (B) The law, regulation, or guidance document described in subparagraph (A) does not need to require critical safety incident reporting to the State of California. (2) The law, regulation, or guidance document is intended to assess, detect, or mitigate the catastrophic risk.

Also on the books in New York

Not frontier-AI law · scope-labelled, linked, not tracked here
Also on the books
NYC Local Law 144 of 2021 (automated employment decision tools)New York City only; hiring and promotion tools, not frontier models — annual independent bias audit plus candidate notice, enforced by DCWP
Official text
This state page is a container: the bill above is the frontier-model law, and these are the other AI statutes on the books, listed with the scope that keeps them out of the comparison. Each links to its official text.