How do I make agent tool calls auditable?

Run evidence stays attachedrun and trace identified
Inspect the run, its trace, reviews, and defining source.

#The question

"How do I make agent tool calls auditable?" has a short answer: make the agent a deployable artifact. With Swirls you declare it in .swirls files, deploy with git push or swirls deploy, and the hosted runtime takes over.

#Who's asking

Security / compliance owner. Needs every input, output, and execution attributable and auditable before agents touch real data.

#Why Swirls is a fit

Agents call deterministic workflows as tools. Each node has a typed input and output schema, so tool execution is scoped, repeatable, and auditable instead of free-form model output.

User and machine executions carry identity, and workflows can include durable human review checkpoints. Workflows are declarative, repeatable, and auditable by construction.

Add the people, data, authority, and decisions around this job.

Keep this solution beside the Apps, records, rules, connections, and reviews it depends on in one .swirls project.