Audit Is a Provenance Chain, Not a Log File
An audit is a provenance chain: what was stored, where each fact came from, and what was used for each decision. This explainer maps the three links that keep agent behavior traceable and fixable.
Loading…
Topic
1 post about Audit. Every summary links to the original.
See the idea
An audit is a provenance chain: what was stored, where each fact came from, and what was used for each decision. This explainer maps the three links that keep agent behavior traceable and fixable.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
To audit what an AI agent knows about a customer, three questions must be answered: what the agent stored, where facts came from, and what it used for each answer. Twilio Conversation Memory stores customer knowledge as traits, observations, and conversation summaries, each with provenance including source, conversation IDs, and revision history. Agent Connect passes retrieved memory to the developer’s code on every message, enabling logging of which memories were used per response, including relevance scores. The guide also covers correcting or deleting incorrect memories and building a persistent audit trail by exporting Memory events via Twilio Event Streams, tied together with conversation IDs. This approach gives human agents and compliance teams the ability to trace, explain, and fix agent behavior, with Agent Copilot displaying knowledge sources.
The best engineering reads, once a week.