Developers · Action lifecycle
The action record is the audit evidence. Follow one from request to result.
Whether a fix to a failing SOC 2 control comes from Deixic or from your own agent, Deixic keeps the actor, target, policy decision, approver, execution, cost, and provenance attached as the action changes state. The same record is what an auditor samples and what your agents read over MCP.
Action record
The fields that decide the call and reconstruct it for an auditor.
- Identity
- Workspace, organization, agent, run, objective, actor, and application
- Tool
- Namespace, name, version, capability, operation, and whether it mutates a resource
- Target
- Connector, connection, provider, resource, and credential reference
- Decision
- Policy references and an allow, deny, or require-approval result
- Approval
- Request, decision, named decider, reason, and decision time
- Result
- Safe output, redactions, duration, resource reference, cost, and provenance digests
Lifecycle
Every terminal state says whether the production tool ran.
- 01Accepted — Deixic has the request and its identity and target context.
- 02Policy evaluating — capability, governance, and gate policy are checked.
- 03Waiting approval — a sensitive call is parked for its assigned owner.
- 04Running — an allowed or approved call executes against the connected system.
- 05Succeeded or failed — output, duration, resource references, and provenance are recorded.
- 06Denied or cancelled — the action ends without the requested production change.
Operator review
The approval and result remain part of the same action.
An approver reviews the target and evidence, and activity history keeps the request, decision, cost, result, and references together.