Proof
Evidence dossiers
A dossier turns the sealed proof into a file someone outside the workspace can use — an auditor, an insurer, a court, a regulator. Each is a ZIP with a content-hash manifest, anchored, timestamped and signed with the workspace’s key; its generation is sealed.
The dossiers
Generate them in Proof › Dossiers. With an API key, the audit dossier is GET /api/v1/journal/export?format=dossier.
curl -o dossier.zip -H "Authorization: Bearer $AZOTH_API_KEY" \
"https://www.azothos.ai/api/v1/journal/export?format=dossier"What every dossier carries
manifest.json: the sha256 of every file, and a root hash over them;evidence.json: the sealed entries and their chain segment, with a readable summary in HTML and PDF;keys.jwks.json: the workspace’s public keys, so its receipts and its signature verify with the ZIP alone;jurisdiction-packs.jsonandmodel-catalog.json: the law packs and the prices the seals name;signature.jwsand, with a time-stamping authority,anchor.tsr, both outside the manifest;- a plain-language notice: how to verify the dossier in three steps, and what a check proves and does not prove.
Decision dossier
Every call of one business decision (X-Azoth-Decision-Ref), with the rule set and the mandate in force that day — from Proof › Decisions, or with POST /api/v1/decisions/export. It restates what was sealed and adds no generated explanation.
Litigation hold
An owner places a hold on designated decisions. While it is active, the purge keeps their traces, a GDPR erasure keeps their envelope and the workspace cannot be deleted. Releasing it takes four eyes; every act is sealed.
Compliance bundles and OSCAL
- For the EU AI Act, the NIST AI RMF, ISO/IEC 42001 (by clause and control number only) and NIS2, each requirement is covered, partial, not covered or out of scope, from sealed evidence, with what is missing.
- Covered means every required group of evidence is met by sealed entries; what only your organisation can provide — an impact assessment, a notice to workers — is never counted as present.
- The bundle ships an OSCAL Assessment Results file, and the verifier refuses a bundle in which a covered requirement lacks a verified citation.
Technical evidence that supports your obligations — never a certification, an attestation of conformity or legal advice. Mappings stay marked “to validate” until an expert reviews them.