> For the complete documentation index, see [llms.txt](https://docs.thegreatwave.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thegreatwave.io/community.md). # Community **Why a DAO?** Investing in The Great Wave is to back and be part of a Decentralized Autonomous Organization that is artist-driven and led in a new creator/investor economy. Creating a DAO allows us to be nimble and adapt accordingly to the times (insert “be like water” Bruce Lee quote), while the appeal of a collective allows us to build strength in numbers and have more influence over the various industries we are in. The format of the DAO is inherently open, inclusive, and accountable, sharing value with the participants who create it. While the beginning phases of any organisation has to be founder-led and driven, we must encourage and elevate contributors’ creativity and contribution in order to progressively move towards decentralisation and allow for more projects to be developed and approved autonomously. We believe that this is key to building a flatter, egalitarian model that will help support artists in this industry. --- # 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.thegreatwave.io/community.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.