vrfy
Check
Proof
Issue and operate
Build and company
check a receipt
vrfy cli · planned interface · not published yet

Prove output.
Persist nothing.

Inspect media against a signed manifest, reproduce the verdict locally, and leave with proof instead of uploaded custody.

opening soon — the cli isn't live yet. nothing was sent. there is no install command today; the commands below are the planned interface.

~/releaseplanned sessionexample
$ vrfy check ./master.mov \
  --manifest ./release.vrfy.json \
  --policy theatrical --no-upload

reading locally ................ 4.8 GB
proof      sha256 + merkle + policy
receipt    vrfy_01M36K0CC81P
example · not live yet · no command here runs
six commands · planned

From policy to signature.

Each command is a step you can run on your own machine once the cli ships. None of them needs an upload.

01 · initializevrfy init --policy theatrical

Pins codecs, loudness, captions, checksum, and signing rules.

02 · manifestvrfy manifest ./master.mov

Builds the expected evidence record without uploading media.

03 · checkvrfy check ./master.mov --json

Returns each check, evidence hash, and exact failure path.

04 · explainvrfy explain vrfy_…

Shows how the verdict was derived from policy and evidence.

05 · reproducevrfy replay vrfy_… --offline

Replays the same verdict from receipt data alone.

06 · signvrfy sign vrfy_… --key release

Adds the release authority signature without changing evidence.

proof receipt · example · not live yet

What you leave with.

A receipt names the job, the policy, the evidence root and the signature. The media stays with you.

proof receiptvrfy_01M36K0CC81Pexample
{
  "job": "./master.mov",
  "verdict": "pass",
  "checks": "14/14",
  "policy": "theatrical",
  "custody": "never",
  "root": "sha256:3a71…",
  "signature": "ed25519:8f3c…"
}
example · not live yet · no receipt was issued

until the cli ships: check a receipt in the browser · replay a verdict · docs

404

Nothing here to check.

check a receipt