Understanding Intent & Confirmations
Learn how Airavat interprets instructions, why confirmations are required, and how to communicate clearly to ensure predictable execution.
Airavat executes exactly what you instruct — not what you meant, not what you intended implicitly, and not what seems reasonable in hindsight.
This page explains how Airavat interprets intent, why confirmations exist, and how to communicate instructions clearly to get predictable outcomes.
What “Intent” Means in Airavat
In Airavat, intent is an explicit instruction that can be translated into a concrete exchange action.
Examples of valid intent:
“Buy 0.1 BTC at market”
“Place a limit sell for ETH at 3,200”
“Close my BTC position”
“Show my open positions”
Airavat treats these as commands, not conversation starters.
If an instruction can be mapped cleanly to a specific action, Airavat will attempt to execute it (subject to validation and confirmation).
Explicit vs Ambiguous Intent
Airavat does not guess.
If an instruction is ambiguous, incomplete, or open to multiple interpretations, Airavat will either:
Ask for clarification, or
Refuse to proceed
Examples of ambiguous intent:
“Buy BTC”
“Reduce my position”
“Take profit here”
“Do something safe”
These statements lack required details such as size, direction, order type, or instrument.
Clarity is not optional.
What Airavat Will Not Infer
To avoid unintended execution, Airavat does not infer:
Position sizing
Risk tolerance
Strategy intent
Entry or exit logic
What “small,” “safe,” or “aggressive” means
If a parameter is not stated explicitly, it will not be assumed.
How Confirmations Work
Before executing any live action, Airavat presents a summary of the exact action it is about to take.
This typically includes:
Instrument
Side (buy / sell, open / close)
Quantity
Order type
Price (if applicable)
You must explicitly confirm by responding yes.
Any other response — including silence — results in no execution.
Why Confirmations Are Strict
The confirmation step is intentional friction.
It exists to:
Catch misinterpretation
Prevent accidental execution
Slow down impulse-driven actions
Make responsibility explicit
If you confirm an action, Airavat assumes it is correct and proceeds accordingly.
Common Intent Mistakes
Most unexpected outcomes trace back to one of the following:
Instructions that are syntactically valid but semantically unintended
Forgetting to specify size or direction
Confusing “close,” “reduce,” and “sell”
Assuming defaults that do not exist
Confirming without fully reviewing the summary
Airavat will execute what is confirmed — not what was assumed.
Intent in Automated or Scheduled Actions
The same rules apply to automation.
When you configure scheduled or recurring execution:
The intent must be explicit
The action must be confirmable at setup time
No new permissions are granted
Automation repeats previously approved intent. It does not invent new actions.
Responsibility Reminder
Every executed action:
Originates from your instruction
Is shown to you before execution
Requires your explicit confirmation
Airavat is not a decision-maker. It is a deterministic execution system.
What’s Next
Now that you understand how intent and confirmation work, the next section covers:
Order types and market mechanics
How exchanges handle fills, slippage, and partial execution
Why execution outcomes may differ from expectations
Precision in language leads to precision in execution.
Last updated