> For the complete documentation index, see [llms.txt](https://alphascan.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alphascan.gitbook.io/docs/economics/roadmap.md).

# Roadmap

If there’s one certainty in startups, it’s the fact that what you plan is definitely not going to happen exactly according to plan. As Eisenhower famously said ‘I have always found that plans are useless but planning is indispensable’. As we designed our roadmap, we have kept this underlying credo close to mind.

Phase 1 (complete):

* Account sentiment analytics
* Token sentiment analytics
* Historical sentiment analytics
* Narratives sentiment analytics

Phase 1b (complete):

* Decentralization&#x20;
* Staking
* V1 tokenomics mechanisms (incl. private/public sales)
* Token indicators for momentum, new & hot, and more

Phase 2 (complete):

* Telegram bot - analytics basics
* Telegram bot - trading
* Additional improved analytics features
* Initial partnership integrations

Phase 3 (complete):

* AI-based analytics model 1
* AI-based analytics model 2

On top of the above listed features, we are planning a few features that will be announced when they are ready for competitive reasons.

<br>


---

# 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://alphascan.gitbook.io/docs/economics/roadmap.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.
