Developers · Action lifecycle
Follow a tool call from accepted request to recorded result.
Deixic keeps the agent, target, policy, approver, execution, cost, and provenance attached as a production action changes state.
Action record
The fields needed to decide and reconstruct the call.
These durable concepts appear together in Deixic action history.
- 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 can review the requested target and evidence before deciding. Afterward, activity history keeps the request, decision, recorded cost, execution result, and supporting references together.