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

# Roadmap

### Overview

Embarking on a transformative journey in the metaverse, the Trumen ecosystem is guided by a structured roadmap, focusing on progressive development phases that encompass technological advancements, user experience enhancement, financial strategies, and community building. Below is a detailed outline of the planned roadmap and prospective stages of evolution for Trumen.

#### Phase One: Internal Alpha Testing (2024/Q1) 

* Selected testers and early waitlist
* Launch a Demo version of Trumen
* llustrating core functionalities

#### Phase Two: Public Testnet Launch (2024/Q2) 

* Testnet token launch on TestFlight
* Mainnet launch preparation
* Building community

#### Phase Three: Public Mainnet Launch (2024/Q4)

• Mainnet launch on AppStore 

• Community and ecosystem growth 

#### Phase Four: Global Launch (2025/Q1) 

• Globally launch with multiple area of marketing focuses

<figure><img src="/files/8RrGxvdybUB2mlcm27bw" alt=""><figcaption></figcaption></figure>


---

# 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://trumen.gitbook.io/truworld/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.