> For the complete documentation index, see [llms.txt](https://stadiax.gitbook.io/stadiax-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stadiax.gitbook.io/stadiax-whitepaper/growing-ecosystem/platform-dao-governance.md). # Platform DAO Governance Users who purchase either an Alpha or Beta Membership will have the opportunity to participate in DAO-like governance activities related to the platform’s existing and future feature set. The governance mechanism will involve different categories for voting on governance proposals, and certain categories of proposals may require holders of Alpha or Beta Membership to hold a certain amount of STADX Tokens to be able to participate in voting. Users who participate in governance have the ability to publicly propose new features and vote on existing proposals. Proposals that receive the most votes, combined with input from the StadiaX Project Contributors may be promoted to official features and incorporated into the platform's roadmap. Similarly, governance can be used to suggest partnerships, marketing activities, or other actions that ultimately serve to enhance the value created for members and platform participants. --- # 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://stadiax.gitbook.io/stadiax-whitepaper/growing-ecosystem/platform-dao-governance.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.