Logs answer “what happened.” Records answer “was it allowed?”
Production agents create a dense trail of prompts, tool calls, API responses, retries, and outputs. That is useful telemetry, but it rarely answers the governance question. The enterprise needs to know whether the agent was hired for this job, allowed to use this credential, supervised by the right manager, and evaluated against the right policy.
That is why ARX treats the audit trail as part of a personnel record rather than a pile of runtime events.
Immutability matters when agents are fast.
Agents can perform many actions before a human understands the consequence. A hash-chained record gives the enterprise a durable sequence: request, policy decision, approval, execution, result, evaluation, and follow-up. If a record changes, verification should fail.
The goal is not decorative cryptography. The goal is to make evidence portable enough for incident review, vendor review, internal audit, and regulatory response.
Termination should be recorded too.
The final proof of control is the exit. When a digital employee is terminated, ARX preserves the revocation event, halted runtime, credential closure, and sealed record state. That termination attestation is often the missing artifact when teams try to prove that an agent is no longer active.
Without those links, the organization has logs. With them, it has accountability.