Skip to content

Audit

The audit section covers how matic records consequential activity across an organization. Policy enforcement, human approvals, agent lifecycle changes, budget decisions, and signal-routing failures all produce immutable, tamper-evident records. Because the audit trail lives in git under .matic/audit/, participants can independently verify governance compliance without relying on a centralized service.

Audit Event Schema

The canonical structure of an audit entry, including required fields, scope annotations, timestamp conventions, and how events reference the actor, decision rationale, and originating context. Audit Event Schema

Consequential Actions

Which actions trigger audit emission and why, including the consequence classification rules that determine when policy applications, guardrail interventions, budget gate decisions, or work assignments become auditable. Consequential Actions

Agent State Transitions

Audit records for every step in the agent lifecycle, from spawning through onboarding, engagement, learning, assessment, suspension, and decommissioning. Each transition captures the triggering authority, rationale, and resulting state. Agent State Transitions

Tamper Evidence

How matic guarantees audit integrity through append-only semantics, git-backed content addressing, canonical path enforcement through the packages/fs layer, and the dual-write rule for HITL decisions. Tamper Evidence

Audit Retention

The retention policy and lifecycle for audit records, including indefinite immutability, queryability through matic audit show, project archival sealing, and continued access to decommissioned agent histories. Audit Retention

Dead Letter Queue Events

Audit entries produced when signals cannot be routed, including placement in .matic/dead-letter/, retry attempts, eventual expiration, and manual rerouting via matic signals route. Dead Letter Queue Events

Remit Bloat Quarantines

What happens when an agent produces output beyond its Work Contract ceiling, including detection during the Validate step, quarantine to wip-assets/, the impact on parsimony Eval scores, and how bloat events feed back into staffing decisions. Remit Bloat Quarantines