Evidence bundle · CTP-260916-0900Sealed · SHA-256
▣manifest.jsonSigned index of every file below, with its hash, size and the time it was sealed
2.1 KB
▣incident/record.jsonSuspicious activity observed · Fifth Avenue Retail, loading dock, east side · documented by a walkthrough officer · sealed Sep 16, 2026, 3:32 PM
sealed
▣media/dock-east-2026-09-16T15-31-40.mp4Preserved from the on-site device the moment it was pinned. Never altered, never re-encoded
hashed
▣media/still-01.jpg · media/still-02.jpgFrames pulled at document time, each hashed separately
hashed
▣notices/trespass-notice.pdfWorded for the state, issued on site, sealed with the record
sealed
▣custody/log.jsonl14 entries: every view, export and handoff, each with a name, a role and a time
append-only
▣redaction/record.jsonWhat was redacted, why, and by whom. Metadata stripped server side
recorded
Manifest hash3f9a1c07e4b2d8f6a51c0e9b7d2f4a86c13e5d09b7a4f2c8e61d3b5a9f0c7e24
Sealed at the source
The record is sealed the moment it is made, at the property, before anyone has a reason to want it changed. The seal is a cryptographic hash, not a promise.
Provenance in the file
Who documented it, when, from which device, on which timeline. The answer to "where did this come from?" travels with the evidence instead of living in someone's memory.
Custody you can read
Every access is logged from the first view to the handoff to your agency. Shared links expire. The log is append-only, and it is in the bundle.
Verifiable by anyone
You do not have to trust BlueWave, the property or the software. Recompute the hashes and compare them to the manifest. The math either agrees or it does not.
Built to be questioned
Admissibility is decided by the court. Provenance is decided by the record. A bundle is designed so that the second question has a clean answer before the first is ever asked.