Hash-chained audit log
Every transformation, decision, policy hit, download, key mint — a tamper-evident block. Each event includes the previous event's hash. Break one and the chain visibly fractures.
The compliance layer underneath every product. Lineage chain, immutable audit log with hash chain, retention enforcement, right-to-erasure orchestration, policy decision point, downloadable evidence packs, EU AI Act mode switch.
Trust is unusual: it's both the substrate every other product depends on AND its own product SKU. Customers running just Trust use it to govern data they already have. Customers running Norm/Dedup/Connect/Agent get Trust included because those products literally cannot run without the audit chain.
Each capability runs in the shared engine — the Norm pipeline, the Trust audit chain, the Decisioning mode toggle. Same substrate as the other four products.
Every transformation, decision, policy hit, download, key mint — a tamper-evident block. Each event includes the previous event's hash. Break one and the chain visibly fractures.
Open Policy Agent under the hood. Your PDP rules, your decisions, your records. Lower priority wins on conflict. System-managed rules can be disabled but not deleted.
Per-job signed ZIP — input hash, output, lineage graph, decisions, retention proof. Downloadable from the dashboard or /v1/trust/evidence-packs.
GDPR Article 17 workflow. Subject submits request, staff approves, the engine cascades the redaction across all derived datasets and writes a tombstone. Chain stays intact; the redacted block is sealed but visible.
The Python SDK is the most mature. TypeScript follows the same shape. Both ship with strict types and async-first APIs.
Same auth as the rest of DAVA: bearer API key on Authorization: Bearer dava_live_… or session cookie + CSRF for browser flows.
We'll run your hardest dataset through DAVA Trust during a 5-day pilot. You keep the cleaned output and the evidence pack either way.