Audit

Audit is the reading side of the two records Daslab already keeps. What ran lives in the job's trace: every tool call, input, output, cost, approval. What changed lives in the scene's commit chain: every state mutation, diffable commit by commit. This page covers what's in them, who may read them, and how long they're kept.

Every call, every approval, every state change

For every tool call:

  • Timestamp (start, end, duration)
  • User ID (and org ID)
  • Scene ID and job ID
  • Tool name and version
  • Inputs (full payload)
  • Outputs (full payload)
  • Cost (for LLM calls and metered tools)
  • Status (succeeded, failed, cancelled, approval-rejected)

For every approval action:

  • Who approved (or rejected, or modified)
  • When
  • What the diff looked like at decision time
  • The agent's reasoning

For every state change in a scene:

  • Which asset changed
  • From what value to what value
  • What job caused the change

Tool calls and approvals land in the trace; state changes land on the commit chain. Both are append-only — recorded, never edited, never deleted. We treat them like git history.

The log stays in your workspace

Logs are stored alongside your scenes, in the same database, scoped to your workspace. We don't ship them to a separate vendor.

You read them in two places: the job permalink (everything one run did) and the scene's history (what changed, commit by commit).

Structured queries instead of transcripts

A chat transcript is a wall of text. To answer "what did this agent do to PO 4500017234 last Tuesday?" you read 200 messages.

A commit chain is a query: filter by entity ID, scope to a time range, get the structured diff. The difference between "log of a conversation" and "log of state changes that happened during the conversation."

Daslab keeps both — read the conversation when you want context. The structured chain is what regulators ask for and what security teams build dashboards on.

The mechanism — content-addressed commits, derived tree diffs — is documented in commit chain.

Audit access follows scene roles

Audit access follows scene roles — owner, admin, member, viewer. If you can see a scene, you can read its history. There is no finer split: operating a scene and reading its history go together.

Nothing is deleted today

Records are retained indefinitely — there is no deletion path.

Data residency and retention.

What's next

  • Approvals — the gate that produces audit events.
  • Data — residency, retention, no-training.

Updated 2026-04-30