See it in action · The Naked Frame

Destroy the file.
The proof survives.

No slides. No animation. A real terminal running commands you can run yourself: a sealed film frame is wrecked, and its full provenance is recovered from the pixels alone.

Real commands · real output · public-domain frame (A Trip to the Moon, 1902)

What you're watching

Three commands, one point.

1

A sealed frame

A film frame sealed by Continuum. ls reports its size: 710,971 bytes, with a known cryptographic hash.

2

The file is destroyed

Resized, recompressed hard, renamed, and stripped of all metadata. The size drops to 9,459 bytes and the hash changes completely. Not one byte shared with the original.

3

Provenance comes back

The verifier runs on the wrecked file, offline. Perceptual distance: 0. It recovers the source, the restoration steps, the consent, and the AI status, from the pixels alone.

Why this matters. Embedded credentials (the standard approach) die the moment a file is re-encoded, because the proof lives in metadata that a transcode strips. Continuum keys the proof to the content itself, so it survives the pipeline. This is the difference between recording provenance and proving it.
Don't take our word for it

Try to break it yourself.

The verifier is a standalone tool that runs offline, with no connection to us. Take a sealed frame, wreck it however you like, and see if the provenance still comes back.