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

# Vision & Roadmap

### Mission&#x20;

* Build a general-purpose recommendation system that can be seamlessly integrated into any Web3 application.

### **Vision**

* Power the new era of sophisticated personalization and tailor-made interactions and experiences across Web3.

### **Milestones & Roadmap**

* Q4’23: Architecture design and team building
* Q1’24: Matching engine statistical model development and soft launch
* Q2’24: Data aggregation and backtesting framework
* Q3’24: Beta Launch of Lucidity’s prediction models for select DeFi protocols
* Q4’24: Addition of asset-level and wallet-level prediction models
* Q1’25: Entity vectorisation and Matching engine v1
* Q2’25: Expansion for NFT marketplaces, SocialFi, and GameFi use cases
* Q3’25: Cross-chain support for AI agent economies and research platforms
* Q4’25: SDK rollout for a general-purpose recommendation system

  <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://docs.lucidity.finance/vision-and-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.
