> For the complete documentation index, see [llms.txt](https://docs.mechaverse.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mechaverse.cc/mechaversedao/route-map.md).
# Route map
#### 2023 Q2:
\- Complete the first phase of Mechaverse development
\- Operate the MMDAO community
\- Launch the MM governance token
\- Launch the MMSwap trading platform
\- Begin the MMDID service
#### 2023 Q3:
\- Launch the second phase of Mechaverse development
\- Launch the NFT marketplace
\- Promote the sale of mech NFT figurines
\- Launch the second auto-battler game
#### 2023 Q4:
\- Launch the third phase of Mechaverse development
\- Launch the third game
\- Promote more mechs and Japanese IP to join
#### 2024 and beyond:
\- Promote the development of more mech entertainment metaverses
\- Launch more games and resources based on mech entertainment metaverses
\- Promote more financial solutions based on mech entertainment metaverses
\- Accelerate the expansion of the MMDAO ecosystem and cooperation with global partners
---
# 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.mechaverse.cc/mechaversedao/route-map.md?ask=&goal=
```
`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.