Audit Logs
The three append-only ledgers, what is recorded in each, and how to read them.
Govula maintains three distinct append-only ledgers, each with its own SHA-256 hash payload. The ledgers are deliberately separated so a corruption in one cannot quietly mask another. A replay verifier recomputes the chain end-to-end and the replay outcome is itself audited.
The three ledgers
audit_log
The primary governance ledger. Every decision and every state-mutating action lives here.
tenant_operation_log
Per-tenant operational events — activation, elevation, configuration changes.
operator_audit_events
Operator-scope events including step-up elevation and capability invocation.
Related
- Audit Readiness — pre-flight checklist before a certification cycle.
- Auditor Walkthrough — the in-platform auditor journey.
- Evidence Semantics — what each field means.
- Control Center — required prerequisite
Audit Logs reference operator surfaces introduced in Control Center.
Next in Operate: Lifecycle Management.
Take the audit chain into a full evidence workflow.
What should I do next?
continues in "operate"
Ranked using IA v1 graph + intent map + glossary density (deterministic; no AI inference).