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

# Roadmap

**Stage 1 - Internal Demo \<Done in 2021 Q4>**

* Testnet for internal review
* Release of demo video to community
* Announcement of celebrity collaborations
* Discord server launch
* Gemie Room Development
* Town Square Development

**Stage 2 - Gemie Planet Early Access \<Done in 2022 Q3>**

* Launch Avatar Customization
* Room Decorations
* Town Square
* Open World Store & Marketplace
* Redemption Center&#x20;

**Stage 3 - Onboarding 1st Phase Partners \<Done in 2022 Q4>**

* Onboarded GEMSTARS: Hanjin Tan, P1Harmony, Cherry Bullet
* Well-known Band BEYOND’s 2FR Band Room built on Gemie Metaverse
* Web3 Partnerships: Qatar World Cup 2022 Digital Twin, Monkey Kingdom, Citypop Tokyo NFT... etc.

**Stage 4 - Game Development & Celebrity NFTs \<Ongoing>**

* Launch celebrity NFTs: P1Harmony, Cherry Bullet
* Metaverse virtual events
* Staking Program
* Expansion of Town Square&#x20;
* Launch branded experiences

**Stage 5 - UGC Fan Planets (Fans Club) & NFTs**

* UGC Fan Planets & NFTs
* Fan planet opens for application
* User-generated NFTs
* User-generated experiences

**Stage 6 - Improve Metaverse Experience**

* Mass celebrity participation
* Launch Gemie DAO
* Develop Mobile version


---

# 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:

```
GET https://docs.gemie.io/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.