ASTRA / Audit trail
The audit trail
Every action ASTRA executes leaves a receipt: what was done, which systems it touched, the moment in the call that justified it, who approved it, when, and how to reverse it. The receipt is hashed, so the record of what happened cannot be quietly edited afterwards.
An agent you cannot audit is an agent you are trusting on vibes. The audit trail is what turns "the AI updated the CRM" into a sentence somebody can actually check.
What is in a receipt?
| Field | What it records |
|---|---|
| Action | The concrete thing that was done, in plain language. |
| Systems | Every tool the action wrote to, not just the primary one. |
| Source | The commitment it came from, quoted, with its place in the call. |
| Approver | The person who said yes, or the standing rule that let a reversible internal write run. |
| Time | When it was approved and when it landed. Those are two timestamps. |
| Hash | A sha256 over the record, so tampering is detectable. |
| Rollback | The path back to the previous state. |
Why verify instead of assuming?
A tool call that returns success proves the request was dispatched. It does not prove the write landed. Field-level validation, a workflow rule, a permission you forgot, a required field on the target object: any of these can swallow an update while every log in the chain still says fine.
So the verify step reads the target system back and compares the new state to the intended one. A receipt is only written once that comparison passes.
What does rollback actually cover?
Reversing a write means restoring the previous value, not writing a compensating guess. For a field change that is the prior value. For a created object it is the deletion or closure of the thing that was created. For a sent mail, honestly, it is nothing, which is exactly why customer-facing mail is gated in the first place and never runs unattended.
Irreversibility is the reason the approval gate exists. The audit trail handles everything after.
Who is the audit trail for?
The rep
Proof that what they promised on Tuesday actually happened, without opening four tabs to check.
The manager
A pipeline review that reads the record instead of reconstructing it from memory.
RevOps
An answer to "what changed this field", which is normally the hardest question in the CRM.
Security
Evidence of what an autonomous system was permitted to do and what it actually did, which are rarely the same list.
What is deliberately not logged?
User-typed content, credentials and personal data do not go into audit logs. The trail captures the shape of what happened, the action, the approval and the target, rather than copying sensitive payloads into a second place they can leak from. More on security and data.
Questions
What does ASTRA log for each action?
The action taken, the systems written to, the commitment from the call that justified it, the approver, the approval and landing timestamps, a sha256 hash of the record, and the rollback path.
Can an action be undone?
Reversible actions can be rolled back to their previous state. Actions that cannot be undone, such as mail already sent to a customer, are gated for human approval before they run, precisely because there is no way back.
Is customer data stored in the audit log?
No. User-typed content, credentials and personal data are kept out of audit logs. The trail records the action, the approval and the target rather than copying sensitive payloads somewhere new.