> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuro-tech.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit trails

> Distinguish ledger history, domain history, and operational events

“Audit log” can refer to three different records on a Neuron. Use the one that answers your question.

| Record                | Answers                                               | Access                                     |
| --------------------- | ----------------------------------------------------- | ------------------------------------------ |
| Domain history        | What happened to this contract, token, or identity?   | Agent API or domain client                 |
| Operational event log | What did this Neuron process, warn about, or reject?  | Administration UI or Event Log MCP         |
| Neuro-Ledger blocks   | Which persisted changes were signed and synchronized? | Ledger administration and authorized peers |

The operational event log is not proof that an object was committed to the ledger. A ledger block is not a substitute for presenting the current signed contract or token history to an application user.

## Application audit checklist

1. Store the domain object ID returned by the Neuron.
2. Store the operation time and the authenticated actor in your application log.
3. Retrieve the object or its history from the owning API when evidence is needed.
4. Correlate failures with Neuron event IDs.
5. Ask the operator for ledger verification only when the assurance requirement calls for it.

Never copy protected contract parameters, credentials, or private ledger content into an unrestricted application log.