⌕
Can We Trust What We See?The Verification Lab
01 / 13The challenge
Episode 5
Case 01 · The challenge

Can we trust what we see?

As synthetic media spreads, telling an authentic recording from an AI-generated one is a serious challenge. Watermarks and provenance data help — but they can be stripped or degraded.

And here's the catch that trips up even careful people: a marker only tells you where content came from. It never tells you whether it's true.

?
Hold this line

A marker signals origin, not truth. Detection tools tell you something was AI-made — not whether what it shows actually happened.

Educational, not legal advice. As of 13 November 2026; EU AI Act focus. Rules and transition periods evolve.
The brief

What you'll be able to do

Case 02 · The toolkit

Two ways to tag synthetic media

Invisible watermarks

A signal hidden inside the pixels or audio, designed to survive editing. Travels with the file itself.

Provenance metadata

Content Credentials log a verifiable creation history — signed records of how the media was made.

Method-neutral. Under European Commission guidance, these aren't the only accepted solutions — any robust, machine-readable mechanism qualifies. The law sets a goal, not a single product.
Case 03 · The limits

Why markers fail in the wild

Metadata gets stripped. Platforms routinely remove it during upload — the provenance record can vanish on the way to the viewer.
Watermarks degrade. Compression and cropping can wear a watermark down until it's unreadable.

But the deeper limit isn't technical. Even a perfect, intact marker answers only one question — was this AI-made? — and stays silent on another: is it true?

Do it · origin ≠ truth

The marker tells you one thing

Click each cell. A marker only reports origin (AI-made or not) — never whether the content is factually true.

Content is TRUE
Content is FALSE
Has AI marker
reveal
reveal
No AI marker
reveal
reveal

Open all four cells.

Knowledge check

A video carries a valid AI watermark. What does that establish?

Case 04 · The EU AI Act

Who has to do what

Providers (Article 50)

Must ensure generative outputs carry machine-readable marks — except for standard assistive editing.

Deployers

Publishing deepfakes or unreviewed public-interest text requires clear public disclosure.

Exemptions & timing. Artistic satire and law-enforcement uses are exempt, with transition periods running into late 2026. And distribution platforms enforce their own rules, independent of the law.
Do it · classify

Provider duty, or deployer duty?

The provider builds the system; the deployer uses it to publish. Sort each obligation.

⚙ Provider

📣 Deployer

Drag a chip into a bucket — or tap a chip, then tap a bucket.

Knowledge check

Under Article 50, ensuring outputs carry machine-readable marks is primarily whose duty?

Do it · verification console

Run the checklist

Because no single marker is enough, verification is a process. Run each check on a suspicious clip.

lab$ select a check to run…
Knowledge check

A clip has no metadata at all. The best conclusion is…

Lab report
0/3

Knowledge-check score

Two approaches. Invisible watermarks (survive editing) and provenance metadata (verifiable history).
Method-neutral. Any robust, machine-readable mechanism qualifies under EC guidance.
Markers have limits. Stripped on upload, degraded by compression — and they never prove truth.
Provider vs deployer. Providers mark outputs (Art 50); deployers disclose deepfakes.
Verify as a process. Metadata → reverse lookup → provenance → context.
Glossary

Watermark — a signal hidden inside media to mark its origin. Content Credentials / provenance — signed metadata recording how media was made. Provider — builds the AI system. Deployer — uses it to publish content.

Educational, not legal advice. As of 13 November 2026.