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: every execution in Swirls produces a tamper-evident audit record of what ran, what triggered it, and what the agent did. Export it and hand it to the client as is.
#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.
Records are tamper-evident and exportable. What you hand the client is verifiable, which changes the conversation from "trust us" to "check it".
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.