π Intent Lifecycle: From Language to Execution
Every user command is treated as an βintentβ, which passes through a defined lifecycle with multiple checkpoints:
π§© Intent States:
parsed
User input has been interpreted by the LLM, with intent + parameters extracted
validated
Syntax and logic of the command confirmed (e.g., correct address, token symbol found)
pending_user_confirmation
Awaiting explicit user approval before sending a transaction
signed
Transaction signed by user wallet (e.g., MetaMask or WalletConnect)
broadcasted
Transaction sent to the network via JSON-RPC
confirmed
Transaction mined and included in a block
failed
Transaction reverted or rejected (e.g., out-of-gas or user declined signing)
Each intent is stateful, and Dialect AI tracks it per user session to allow conversational context like:
βWhat happened to the token I was trying to deploy?β
Last updated