Proof
The journal, the receipts, the timestamps
Every decision, served or refused, is sealed in a per-workspace, hash-chained, append-only journal, and the client keeps its own signed receipt of each one. Anyone can check both without Azoth.
The sealed journal
- Each entry hashes the previous one:
entry_hash = sha256(prev_hash || core_canonical). Changing or removing an entry breaks the chain from that point on. - Refusals are sealed too: Azoth proves what it blocked. A seal holds non-personal facts — ids, codes, hashes, the rule set, the law, the price, when it was decided, the kind of actor and the trace — never the prompt or the answer.
- Personal data sits in a separate envelope that can be erased under the GDPR without breaking the chain.
- The chain is verified every hour as it grows — the new entries, and the last verified one still there, unchanged — and in full, every entry recomputed from the first one kept, once a week and on Verify now; a break is shown in Proof and raised as an alert.
- Read it in Proof › Decisions — each outcome with its detail: the rules, the security verdicts, the grounding check, the routing, the law — or with
GET /api/v1/journal.
Receipts
Every answer of the gateway that is not streamed carries X-Azoth-Receipt: a compact JWS signed with the workspace’s Ed25519 key. Even if Azoth is gone, it proves that Azoth decided this — and lets an auditor find the decision in the chain. A streamed answer carries none: its headers leave before its decision is sealed, when the stream ends (a stream that ends in error is a failed call, never sealed).
header { "alg": "EdDSA", "typ": "azoth-receipt+jws", "kid": "<RFC 7638 thumbprint>" }
claims { "v": 1, "ws": "…", "trace": "…", "core": "<sha256>", "out": "allowed", "iat": 1793750400 }What a receipt says
wstracecoreoutallowed, blocked, rerouted, held or failedrefiat- Never any content. A streamed answer carries no receipt yet; it carries
X-Azoth-Trace-Id. - A served answer has a receipt while the decision journal is on; a refusal always has one. A receipt never makes a call fail.
- The public keys are a JWKS at
GET /api/proof/keys/<workspaceId>, retired keys included. Keys rotate every 90 days.
import { receiptOf, verifyReceipt } from '@azothos/sdk';
const jwks = await fetch(`https://www.azothos.ai/api/proof/keys/${workspaceId}`).then(r => r.json());
const claims = await verifyReceipt(receiptOf(response), jwks); // null when it does not verifyOne business decision, many calls
Send X-Azoth-Decision-Ref — an id your system already has, like a credit file number, never personal data — on every call that serves one decision. Azoth keeps only a hash salted per workspace, and gathers those calls into one decision dossier.
await openai.chat.completions.create(body, {
headers: azothGatewayHeaders({ decisionRef: 'CREDIT-2026-000123' }), // an opaque id
});Trusted timestamps
- An RFC 3161 time-stamping authority signs each exported dossier’s root hash and, every 5 to 60 minutes, each workspace’s chain head. Only a SHA-256 digest leaves Azoth.
- Three levels per workspace: standard (the deployment’s authority), qualified (an authority the workspace names, tested before it is saved) and local (the operator’s own, outside SaaS).
Client vault
For a system in vault mode the gateway keeps no content of its calls — no journal envelope, no semantic cache — and answers X-Azoth-Vault: on. The SDK encrypts the content with your key into your own storage and posts a receipt; Azoth seals only its hashes.
Grounding check
Send the passages an answer must rest on, and Azoth estimates the share of its statements they support, at the stakes of the system: sampled after the answer, returned with it, or checked before it leaves. The score is always an estimate, shown with its judge’s measured agreement with people. The passages are never stored.