How to verify this dossier
Azoth produced this dossier from a workspace’s sealed journal. You can check for yourself — without trusting Azoth, or the organisation that handed it to you — that it was not altered and that it existed on the date it states.
What it holds
the sealed decisions of a period, and how the law applicable to the workspace was covered.
Three steps
- Download the workspace’s public keys yourself, from Azoth and not from this dossier: /api/proof/keys/<workspace>. Open the offline verifier — the « azoth-verify.html » page (one page, which connects to nothing) or the « azoth-verify » command-line tool — and give it the ZIP file as you received it, with those keys (« --keys »).
- Read the verdict. The dossier is verified when every file matches its hash (manifest.json), the chain of decisions is intact and it is signed by one of the keys you gave. A dossier without a signature, or signed only by the key it ships itself, is not verified: anyone could have rebuilt it. Each check is listed, with what it found.
- Look at the date and the author. « anchor.tsr », when present, is the token of an independent time-stamping authority (RFC 3161): the dossier existed on that date. To trust it fully, give the verifier the root certificate that authority publishes (« --tsa-root »). « signature.jws » is the dossier signed with the workspace’s key; it also commits what the dossier covers — the journal’s head when it was exported, the decisions listed, the export’s filters: the verifier says how many later decisions are not in it.
What the check proves
- The files are the ones produced, without any change.
- Each listed decision was sealed at its position, in order, with nothing inserted or removed — and neither the first nor the last ones were cut after signing: the dossier covers what its signature states.
- The dossier existed on the date of its timestamp, and it was signed with the workspace’s key.
- A receipt handed back with an answer verifies with the same keys: « azoth-verify receipt <receipt> --dossier <this dossier> --keys <keys> ».
What it does not prove
- That the decisions were right, or lawful: the dossier reports what was decided and sealed; it does not interpret it.
- This dossier is technical evidence supporting obligations. It is not a certification, an attestation of compliance or legal advice.
« anchor.tsr », « tsa-chain.pem » and « signature.jws » are outside the manifest: they bear on its root hash, which covers every other file.