How do I give clients an audit trail for their agents?
#The question
If you are asking "How do I give clients an audit trail for their agents?", you want evidence you can hand over, not assurances. The short answer: Swirls records execution identity, trigger, steps, and outcome, and emits append-only operational audit events you can export for the client.
#Who's asking
Managed service provider / agency. Operates agents on a client's behalf, and the client, their auditors, or their security team wants proof of what happened.
#Why Swirls is a fit
The audit trail is produced by the runtime, not by your discipline. Every execution records its trigger, its steps, and its outcome as it runs. There is no instrumentation for your team to remember and no gap when someone forgets.
Execution records and audit events are exportable, so what you hand the client is concrete evidence they can inspect line by line, not a summary they have to take on faith.
Identity is part of the record. Executions carry who or what initiated them, so the trail answers the client's real questions: what ran, on whose behalf, and with what result.
#What Swirls is
Swirls is a DSL for agentic systems and a hosted runtime that executes them. You write .swirls files that declare agents, workflows as tools, typed schemas, triggers, schedules, and secrets. Authoring is local and free. Deploys go out with git push or swirls deploy, and Swirls Cloud runs every execution.