Evidence and auditing

Axec records a tenant-scoped evidence trail for governed actions. An ActionRequest receipt orders that evidence around one correlation identifier.

What a receipt can show

• request acceptance or idempotent deduplication
• final action-policy outcome, reason code, evaluator version, snapshot digest, surface, and sorted matched rule keys
• approval eligibility outcome, reviewer decision, and expiry
• credential-use intent, dispatch boundary, and upstream outcome when Axec mediated the operation
• Data Protection revision, matched policies, profile categories, masking outcome, bounded redaction counts, and stable failure reason
• terminal ActionRequest state

This is enough to answer who requested an action, what governed capability or normalized target was involved, which controls applied, whether Axec dispatched it, and how the governed request ended.

What evidence excludes

Evidence and receipts do not contain credentials, authorization headers, raw MCP arguments, unrestricted query values or request bodies, unrestricted upstream bodies, detected sensitive values, or encryption material. Result retrieval returns a bounded sanitized result only when the requester is authorized and the result remains within retention.

A credential-release record proves that Axec released a credential. It does not claim visibility into, policy enforcement over, or Data Protection of later requests made directly with that credential.

Investigate an incident

1. Start with the ActionRequest correlation identifier and terminal state.
2. Verify the admitted principal, OAuth client, optional workload actor, gateway, Connector, surface, and operation scope.
3. Compare policy rule keys and snapshot digest with the configuration active for that evaluation.
4. If approval was required, confirm the eligible reviewer, decision, expiry, and identical client continuation.
5. Check whether dispatch began and whether upstream outcome is known.
6. Review Data Protection policy revisions and sanitization outcome without requesting raw response samples.

If required decision or pre-dispatch evidence cannot be committed, Axec fails closed before decrypting a credential or contacting upstream. Evidence therefore marks both an audit boundary and part of the execution safety boundary.