Responsible AI Safety and Education Act (RAISE Act)

Notas

The definition that puts this instrument in the register

“Critical safety incident”, quoted in full from the codified text of General Business Law section 1420:

Unauthorized access to, modification of, or exfiltration of, the model weights of a frontier model that results in death or bodily injury; Harm resulting from the materialization of a catastrophic risk; Loss of control of a frontier model causing death or bodily injury; or A frontier model that uses deceptive techniques against the frontier developer to subvert the controls or monitoring of its frontier developer outside of the context of an evaluation designed to elicit this behavior and in a manner that demonstrates materially increased catastrophic risk.

Shared drafting. California’s SB 53 defines “critical safety incident” in word-for-word identical terms. See us-ca-sb-53-tfaia. Both texts were retrieved in full on 2026-10-05 and compared. This register treats them as one drafting adopted twice, not as two states independently reaching the same judgement, because presenting the same sentence from two legislatures as two datapoints would overstate the evidence.

Why regulates is recorded as developer

Confirmed on the codified text. “Frontier developer” is defined at section 1420 as:

A person who has trained, or initiated the training of, a frontier model.

The duty keys on training. That is the opposite of the covered-entity test in us-ai-kill-switch-act, which keys on operating and serving and is recorded as unclear. The two sit on the same register for that reason.

Also from section 1420: “Frontier model” is “A foundation model that was trained using a quantity of computing power greater than 10^26 integer or floating-point operations”, and “Large frontier developer” is “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”.

No shutdown or disable requirement

Nothing in the retrieved records or the codified definitions requires a frontier developer to shut down, halt, suspend or disable a model. This instrument is tracked on the incident-reporting limb only.

The operative version

The operative version is the chapter amendment, not the bill as first signed. S.6953-B was signed on 2025-12-19 as chapter 699 of 2025. A.9449, signed on 2026-03-27 as chapter 96 of 2026, replaces article 44-B entirely and sets the effective date, quoted from the Assembly record as “This act shall take effect [on the ninetieth day after it shall have become a law] JANUARY 1, 2027.”

Scope caveat

Only section 1420, the definitions section, was retrieved in full. Sections 1421 to 1429 were listed by title — Transparency requirements, Reporting, Loss of equity, Duties and obligations, Scope, Exceptions, Violations, Large frontier developer disclosure, Rulemaking authority — but not read. Their contents are not described here.

Source composition

Three of the four sources above share one publisher, the New York State Senate. The gate is met on unique publishers rather than on source count: the Office of the Governor of New York is the second distinct publisher.