> For the complete documentation index, see [llms.txt](https://docs.teaproject.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teaproject.org/_z_faq/governance-structure.md). # TEA Governance Structure * The TEA community is governed by a DAO management structure. * The TEA Project DAO encourages decentralized decision making through granting voting rights to locked T tokens. * All decisions are made by the DAO solely through voting. TEA and CML are not governance tokens. The following types of ecosystem participants who stake TEA earn votable reputation tokens: * Miners (state maintainers and CML miners who pay the state subscription fee). * TApp devs (who pay the memory tax). * Investors (who lock their TEA into either TApp or CML bonding curves). Note that CML miners who don't pay a state subscription fee will still earn voting privileges based on their own investment in their CML token. Each of the above class of users earn reputation tokens that they can use to vote (spend) on governance issues. More info is available here: --- # 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.teaproject.org/_z_faq/governance-structure.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.