Demos should produce evidence, not applause.
Start with the complete producer-to-receiver handoff. The scenario walkthroughs explain why the protocol exists; the runnable proof shows the exact commands, artifacts, signatures, policy decisions, and failure reports a recipient can inspect.
Source bytes to an independently verified handoff
Create and sign an origin, apply two transformations, sign a manifest, transfer the bundle, and verify it under receiver-owned schemas and signer policy. Then run seven deliberate failures: edited metadata, mutated final bytes, rewired steps, removed predecessors, wrong statement digests, unauthorized signers, and private-profile violations.
- RUNOne local commandRebuild every artifact deterministically.
- PASSOne allowed handoffAll receiver checks hold.
- DENYSeven failuresEach closes for a named reason.
Scenario walkthroughs
- 01
Poisoned pipeline
Corrupted sensor input is accepted silently until signed lineage makes the source and blast radius inspectable.
Walk through → - 02
Reproducibility gap
A published result survives staff turnover because the source, processing steps, and exact output remain connected.
Walk through → - 03
Provenance on release
Automation binds a published dataset to its inputs and build evidence instead of relying on a forgotten manual step.
Walk through → - 04
Configuration postmortem
An incident responder finds the exact configuration and processing step that changed downstream data.
Walk through → - 05
AI dataset gate
A training pipeline rejects data whose labels, source, processing claims, signers, or final bytes cannot be verified.
Walk through → - 06
Invisible Unicode
A content profile catches hidden codepoints that signatures faithfully preserve but cannot judge as safe.
Walk through →
Every persuasive demo should be reproducible by someone who did not build it.
The reference proof, fixtures, schemas, and verifier are maintained in the core repository. No service account or hidden hosted verifier is required.