> For the complete documentation index, see [llms.txt](https://hashguardians-2.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hashguardians-2.gitbook.io/whitepaper/directory/cnft-universe.md). # CNFT Universe The information described in the previous sections represents the core functions of the HashGuardians gameplay and the interactions of the Cardano blockchain with our NFT based gaming economy. This will be the foremost priority as we develop the gaming platform and grow from an early startup into a fully functional platform.\ \ Our full vision for the HashGuardians Universe, however, does not end there. When we speak of the HashGuardians Universe, we do mean a universe – one that is filled with a wide variety of creatures and characters. Our full vision is to develop an open universe inclusive of other Cardano projects. One where owners of other 2D character based NFTs can directly enter, play, and participate with their HashGuardian friends. We want to build a complete ecosystem for Cardano 2D projects, giving everyone a chance to hang out, play and earn in the form of NFTs, and have fun together!\ \ There are many milestones to achieve and goals to accomplish in reaching this vision, but we remain dedicated and determined in our efforts to make it a reality. --- # 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://hashguardians-2.gitbook.io/whitepaper/directory/cnft-universe.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.