> For the complete documentation index, see [llms.txt](https://docs.gamedao.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gamedao.co/getting-started/realms.md). # Realms If you're a game developer using ZERO Network or making use of GameDAO's platform, you'll have access to Realms. These are simple mechanisms to qualify your projects and cluster them into segments. On ZERO, you'll be able to manage aspects and analytics of your game. On GameDAO, similar to a namespace, your **Realms** will provide information about your **DAO** and assets belonging to it, allowing you to easily manage and visualise data relating to your campaign or organisation. Realms are divided into two categories, Open and Discover ### Open Any creator can deploy a project to be listed in the open category. By nature, projects in the open category can deliver a wide variety of qualities. ### Discover Projects in the discover category are handpicked by the community through a curation process: They qualify for direct support by the GameDAO Treasury, Launch Support and listing in the Storefront. --- # 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.gamedao.co/getting-started/realms.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.