✓ Local verification  ·  No upload required

Verify a CaseLedger evidence bundle.

Reviewers can check hashes, signatures, audit records, timestamp tokens, and the signed bundle seal — without buying the recorder or sending confidential recordings to a server.

What to ask for.

Ask the sender for the complete .evidencebundle folder. If they need to send one file, they should ZIP the whole folder. The MP4 alone is not a complete evidence package.

Three steps. That's it.

§ I · OPEN

Open the bundle

Use the free CaseLedger Verifier app and choose Open Evidence Bundle. The verifier walks every required check.

§ II · REVIEW

Review every check

Verified means required hashes, signatures, identity, audit, inventory, and content-seal checks all passed.

§ III · ESCALATE

Treat failures seriously

If a required check fails, treat the bundle as changed or incomplete unless the sender can provide a clean copy.

Command-line verification.

Use the CLI locally or in an intake workflow. JSON output makes it easy to drop into existing review pipelines.

Terminal · macOS
# Standard human-readable output caseledger-verify /path/to/Recording.evidencebundle # JSON output for automation caseledger-verify --json /path/to/Recording.evidencebundle

What verification proves.

Verification proves the files in the bundle match the signed evidence package and have not changed since signing. It does not prove that the screen content itself is true, complete, or automatically admissible in court.

Privacy

Verification runs locally. The verifier does not upload the recording, manifest, audit log, or evidence metadata.