Audit
Audit logging happens at two levels, and they’re currently separate.
The runtime’s audit trail
Section titled “The runtime’s audit trail”Every tool call, every proposal decision, every run — the runtime writes it
to a durable, append-only log (.ravel/audit.jsonl) as it happens. This is
the same log whether the team is running on your laptop via ravel serve
or inside a worker in production, because it’s the same runtime. Streamed
verbosely with -v / --verbose, or watched live over SSE from the
operator console.
This is the log to reach for when you need to know what an agent actually did — which tool it called, with what input, and what a human approved or rejected.
The platform’s audit trail
Section titled “The platform’s audit trail”Separately, the platform records its own tenant-level events — deploys and budget breaches are wired in today, attributed to the person or process that triggered them. This is a backend capability: the events are recorded and queryable, but there is no dashboard page for browsing, searching, or exporting them yet. If you need that today, it isn’t there — this is an honest gap, not a hidden one.
- Spend governance
- Connect a repo — where the deploy-level events come from