Audit History
Last updated September 21, 2026
Use Matruno audit logs, matter timelines, notes, webhook delivery records, external tool traces, and agent logs to reconstruct legal execution history.
What the audit history should answer#
An audit or history record should help answer:
- What changed?
- Who or what initiated it?
- Which matter, legal review task, or workflow did it affect?
- When did it happen?
- Which saved event, note, webhook delivery, tool call, agent log, or task transition supports that answer?
Implemented history surfaces#
The repository includes:
AuditLogfor business events and matter timelinesUserAuditLogfor auth/user events- matter timeline routes under
/api/v1/matters/{matter_id}/timeline - notes and matter notes
- agent execution logs and moderator logs
- automation execution logs
- webhook delivery records
- external tool execution traces
- Temporal workflow histories through Temporal UI
Avoid reasoning-trail language#
Audit history records system events and persisted outputs. It does not expose hidden model reasoning. Use "agent execution log," "tool execution trace," "matter timeline," and "audit history" when documenting explainability.
Audit review belongs in regular operations
Review audit and execution history during normal operations, not only after incidents. Repeated task retries, webhook failures, or manual overrides often reveal workflow design issues.
Was this helpful?