An AI agent's audit trail holds five groups of fields. Each field is there because a question cannot be answered without it.
Who and with what permission. The principal who started the decision, as a pseudonymous ID; the agent's identity and version; the permission scope it acted under; the trace and session IDs; and, for a sub-agent, who delegated to it and with what scope. Without these, "who did this?" has no answer, and neither does "was it allowed to?". Designing the identities themselves (tokens, OAuth, service accounts) is a separate service, Agent Identity & Access Control.
What it saw. The request and the retrieved sources, as references into the content store, with redactions applied by your rules. Without them, a bad answer cannot be told apart from a bad source.
What produced it. The model and its version, the prompt and settings version, the platform and the route. Without them, a change in behaviour cannot be tied to a change on your side.
What it did. Tool calls with their arguments and results, actions refused or denied, the guardrail decision, and the approver where one was required. Refusals and denials are records too: a trail that keeps only what happened cannot show what was stopped.
Output and time. The output, as a reference, and when the decision started and ended.
Why references, not content. The integrity check covers the records. If personal content sat inside them, an erasure request or a retention deadline would force a choice between deleting it and keeping the check intact. With content in a separate store, linked by reference, it can be deleted on its own schedule while the record and its check stand. For you, the records stay personal data: pseudonymised data that can be linked back is personal data (Recital 26).
Why reasoning text is not the record. Some models write out their reasoning. It can be kept as a reference, but it is not treated as the account of why the agent acted: in a 2025 study, Chen and colleagues found that reasoning models' written reasoning often left out a hint the model had in fact used. The record keeps what can be checked: inputs, tool calls, decisions and outputs.