79TH UNIT · CLEARSKY
LOG IN FOUNDING MEMBER
Verifier · Citation

How to cite a CLEARSKY dossier.

A citation is a recipe for re-derivation. If a third party can follow the citation and arrive at the same verdict, the citation is good. We recommend a single format and stick to it.

§01Format

The recommended citation is a single sentence. It carries four things: the document id, the verdict, the public verification URL, and the date and time you checked it.

CLEARSKY dossier {doc-id}, verdict {VERDICT},
verified at https://verify.clearsky.79thunit.co.uk/v/{doc-id}
on {ISO-8601 date-time}.
  • {doc-id} is the document id printed on the dossier. It is a UUID. Quote it in full; a truncated id will not resolve.
  • {VERDICT} is the string the public verifier returned when you checked: VERIFIED for a genuine, unaltered document. An unknown id returns not found. Only cite a document that returned VERIFIED at the time of citation.
  • The URL is https://verify.clearsky.79thunit.co.uk/v/{doc-id}. It resolves in any browser. No account is required.
  • The date is when you ran the check, in ISO 8601, UTC. The verdict is a statement about that moment; the reader re-runs the check at theirs.

§02Example

Illustrative only: the document id below is a format specimen, not a registered document, and will return not found if queried.

CLEARSKY dossier 3f6c9d2e-7a41-4b8a-9c05-1e2d8f4a6b7c,
verdict VERIFIED,
verified at https://verify.clearsky.79thunit.co.uk/v/3f6c9d2e-7a41-4b8a-9c05-1e2d8f4a6b7c
on 2026-07-15T09:30:00Z.

For witness statements and exhibits, cite the dossier in the body of the statement and exhibit the verifier verdict in an appendix: a dated screenshot or print of the verdict page at the verification URL.

Any party can re-run the check at any point in proceedings, without an account and without contacting us. Verification requests are logged for audit (time, document id, outcome); we do not publish who verifies.

We do not opine on admissibility. That is for the instructing solicitor.

§04Academic

For academic and research work, prefer the long form. Every field in it comes from the public JSON envelope at GET /v/{doc-id}/json: the signing timestamp (signed_at) and the signing key fingerprint (signing_key_fp). The signing public keys are published at verify.clearsky.79thunit.co.uk/.well-known/clearsky-verifier-keys.json.

CLEARSKY (2026). Dossier 3f6c9d2e-7a41-4b8a-9c05-1e2d8f4a6b7c.
Signed {signed_at from envelope}, key {signing_key_fp from envelope}.
Verdict VERIFIED, checked 2026-07-15.
https://verify.clearsky.79thunit.co.uk/v/3f6c9d2e-7a41-4b8a-9c05-1e2d8f4a6b7c

Do not quote a document hash in a citation. The public envelope does not publish one. The verifier proves integrity by re-checking your copy's bytes against the recorded signature, not by asking readers to compare hash strings by eye.

§05Re-deriving the verdict

What a reader does with your citation:

  1. In a browser: open the verification URL, or paste the document id at the public verifier. No account is required.
  2. By machine: GET /v/{doc-id}/json returns the signed envelope.
  3. Holding the PDF itself: POST /v/{doc-id}/verify re-verifies the uploaded document bytes against the recorded signature.
GET  https://verify.clearsky.79thunit.co.uk/v/{doc-id}          verdict page
GET  https://verify.clearsky.79thunit.co.uk/v/{doc-id}/json     signed envelope
POST https://verify.clearsky.79thunit.co.uk/v/{doc-id}/verify   re-verify PDF bytes

Behind the verdict: dossier finalisation is gated on analyst confidence, the canonical dossier bytes are hashed SHA-256, and the hash is signed with an ECDSA P-256 key. The maths is laid out on the baseline page; the reasoning on the manifesto page.