Audit Event

Immutable evidence of who attempted or performed an action, why, and with what result.

Reviewed: July 2026
Current state: Audit records exist across canonical mutations, permissions, correspondence, and administration with varying schemas.

Owning boundary: Applicable application or Kernel audit boundary
Not equivalent to: Domain Event · Integration Event
Verified identifiers: auditEventId

An Audit Event preserves accountability for an action or attempt. A rejected Command can create audit evidence even when no canonical business fact changes.

Related guidance

What is the difference between a Command and a Domain Event?

How does Kernel correct a mistake without rewriting history?

Command

Domain Event

Provenance