11Control
Execution Lifecycle
Eight visible, auditable steps from observation to reconciliation, and what happens when one fails.
Every supported action moves through a visible, auditable sequence.
Transaction sequence
- Observebalances, positions, prices, market conditions
- Proposestrategy creates a typed transaction candidate
- Simulatecompute expected state transitions and costs
- Validateenforce policy, exposure, assets and timing
- Authorisebounded agent signer signs the payload
- Submitaccount execution and protocol interaction
- Settleawait receipt and record the actual outcome
- Reconcileupdate ledger, limits and user-facing history
Failure handling
A rejected candidate never silently retries with broader privileges. A failed on-chain transaction may consume gas without achieving the intended action. Pending transactions are tracked by nonce to avoid duplicate execution. Multi-step actions treat partial completion explicitly.
Order and state identifiers
Your activity history links the NFT token ID, account address, signed policy ID, transaction hash or venue order ID, proposed notional, executed notional, fee entries and outcome status. Private inference context need not be on-chain. Economically consequential settlement must be independently verifiable.
Service availability
Automation depends on monitoring processes and external network connectivity. You retain a direct on-chain recovery path even when the agent service is unavailable. Continuous uptime and exact-time execution are not unconditional promises.