Verifier demo
Sample verdict for the
demo dossier.
This is what a recipient sees when they paste the document ID for the sample dossier into the public verifier. Verdict, signed envelope, key fingerprint, signed-at timestamp, and the public-key pin block.
Verification result
Verified
- doc_id
- sample-mp-2026-demo-fbe8d31b-9a4c
- signed_at
- 2026-04-15T14:53:21Z
- kind
- family_law_locate_dossier
- signed_by_role
- supervisor
- alg
- ES256 (ECDSA P-256)
- key_fp
- sha256:01a3:9c2e:bb47:4d18:demo:demo:demo:demo
- signature
- 30450220…DEMO…sample…0221008af3e1b27c
- case_id
- SAMPLE-MP-2026-DEMO
- payload_hash
- sha256:8f4d:ca91:7e3b:dd59:7a02:18b6:c4f3:a201
- verifier_url
- verify.clearsky.79thunit.co.uk/v/sample-mp-2026-demo-fbe8d31b-9a4c
- revoked_at
- (not revoked)
Public keys are served on the verify subdomain at
verify.clearsky.79thunit.co.uk/.well-known/clearsky-verifier-keys.json.
Pin them once and verify offline forever. The fingerprint shown above
is a demonstration key; production fingerprints differ.
What this proves
Three things a real verdict tells you.
-
01
The dossier was signed by the 79th Unit. The ECDSA signature on the file matches our public key, the fingerprint of which is published at the well-known endpoint shown above.
-
02
The dossier has not been tampered with since signing. The payload hash matches what was signed. Any change to the document body invalidates the signature and the verdict shows "Tampered".
-
03
The dossier was signed at the timestamp shown. The signed-at value is part of the signed envelope. It cannot be backdated or postdated without breaking the signature.
What this does NOT do
- It does not reveal the contents of an investigation to the public.
- It does not reveal analyst identities (only the signing role).
- It does not reveal subject identities of ongoing investigations.