Evidence and compliance
Kavros treats evidence as a product: every governed decision, approval, and block lands in a tamper-evident, hash-chained audit log you can export and verify yourself.
The hash chain
Audit records chain cryptographically — each record's hash covers the previous one. The dashboard's audit view supports verification, and exports carry the chain so an auditor (or your script) can confirm nothing was edited or dropped after the fact.
SOC 2 style exports
- Filterable, searchable, paginated audit exports (JSON or CSV) with actor, action, timestamp, and chain hash —
- policy approval timelines with proposer and approver identities,
- incident timelines from creation through resolution,
- enclave attestation records for protected actions.
Framework evidence packs
Evidence packs assemble the artifacts a control framework asks for — access reviews, change approvals, incident handling, data-protection checks — from the records the platform already produces. They speed the conversation with your auditor; they do not, by themselves, make you compliant — the honest boundary, stated up front.
Executive reporting
The executive pack condenses the deployment's posture — agents governed, actions blocked, spend under management, incidents and their resolution — into a form you can forward without redaction work.
Verify it yourself
# export from the dashboard, then check the chain locally
kavros explain 403 --body '{"error":"Blocked by Kavros", ...}'
# → what happened, whether anything reached the target, what to do next
The same plain-language rule applies to evidence: every record should be readable by the person who has to act on it.