> For the complete documentation index, see [llms.txt](https://aikaverse.gitbook.io/aikaverse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aikaverse.gitbook.io/aikaverse/inside-aikaverse/aikas-architecture/intent-system.md).

# Intent System

## Intent System: Decision-Making with Precision

The Intent System is Aika’s **cognitive layer**, responsible for decision-making. Using hierarchical intent classification models, it processes and prioritizes user requests with sub-second response times.

### Key Intent Types

#### Confirmation Intents:

* `ConfirmBuy`, `ConfirmSell`, and `ConfirmTransfer` summarize requested actions for user validation.

#### Execution Intents:

* Executes buy/sell orders, transfers, and other transactions based on previously confirmed intents.

#### Clarification and Error Intents:

* Dynamically refine incomplete inputs or provide alternative solutions for unsupported requests.

### Safety Features

* **Context-Aware Logic:** Ensures execution intents always reference validated confirmation intents.
* **Chain-Integrated Validation:** Verifies user balances, chain compatibility, and market data before execution.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://aikaverse.gitbook.io/aikaverse/inside-aikaverse/aikas-architecture/intent-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.