Trump administration announces funding for PTSD research on ibogaineWIRED investigation examines Jensen Huang's comments on defining women's power in techWalmart launches early Black Friday promotions on select giftsMint Mobile offers $500 discount on select new phones for new customers signing up for a yearRussia and Iran criticize U.S. Caspian task force amid reports of joint sanction evasion effortsNewly elected US lawmakers pose for traditional group photo at Capitol ahead of 120th Congress openingUS existing home sales drop to lowest monthly level in yearsPro-Palestine philanthropist faces US extradition hearing in SpainLewisham Islamic Centre criticizes charity watchdog over warning on Palestine commentsSenegalese wrestlers succeed in beach wrestling at Dakar Youth OlympicsUS nonprofits file lawsuit seeking pause on advanced AI model trainingDemocrats convene in Denver to discuss party direction after midterm victoriesUS releases report on $12bn from Venezuelan oil, mineral resourcesPope Leo XIV urges Catholic Church to address clergy sexual abuseShooting near White House results in death, suspect later found dead
All fact checks
AI analysis

Fact check

“California’s SB 53, New York’s RAISE Act, and Illinois’s SB 315 require AI developers to report “critical safety incidents” defined as incidents that cause more than 50 deaths or physical injuries or $1 billion in damage.”
DisputedConfidence: MODERATE

Reasoning

One excerpt from MIT Technology Review states that California’s SB 53, New York’s RAISE Act, and Illinois’s SB 315 require AI developers to report “critical safety incidents” defined as incidents causing more than 50 deaths, physical injuries, or $1 billion in damage. However, two other excerpts from the same source describe SB 53 and the RAISE Act as only requiring a safety framework and not mandating such incident reporting, and note that only Illinois’s SB 315 includes an audit requirement. The contradictory information prevents a clear verification of the claim.

On confidence: The evidence contains both supporting and contradicting statements about the reporting requirements and definitions in the cited laws.

Important context

The claim hinges on the specific language of the three bills. While one passage attributes a detailed reporting definition to all three, other passages suggest that only Illinois’s SB 315 includes stringent reporting/audit provisions, and that SB 53 and the RAISE Act focus on safety frameworks rather than incident thresholds.

Evidence

Supporting (1)

  • Tier 1 — Primary source
    Who’s liable when AI agents go rogue? | MIT Technology Review

    these incidents. (OpenAI did not respond to a request for comment.) State AI transparency laws like California’s SB 53 , New York’s RAISE Act , and Illinois’s SB 315 require that AI developers report “critical safety incidents.” These are…

Contradicting (2)

  • Tier 1 — Primary source
    Who’s liable when AI agents go rogue? | MIT Technology Review

    auditor. California’s SB 53 and New York’s RAISE Act just require AI companies to publish a safety framework describing how they will test their models for dangerous capabilities and then to follow it. The frameworks are written by the…

  • Tier 1 — Primary source
    Who’s liable when AI agents go rogue? | MIT Technology Review

    required AI companies to report a broader set of safety incidents (including incidents in which a model acts on its own or slips its controls), undergo annual third-party audits, and maintain a kill switch. But after a year of intense…

Limitations

All evidence comes from a single article, and the excerpts provide differing interpretations of the legislation. No direct text from the bills themselves is provided, limiting the ability to confirm the exact legal requirements.

Last verified:
Sep 30, 2026, 7:48 PM CDT
Pipeline:
2.1.0
Claim type:
Factual

Where this claim appeared

Who’s liable when AI agents go rogue?

MIT Technology Review · Michelle Kim