> For the complete documentation index, see [llms.txt](https://docs.tea.xyz/tea/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tea.xyz/tea/i-want-to.../learn-about-the-teadao.md).
# Learn about the teaDAO
The teaDAO is a mechanism that governs the tea protocol. It allows protocol users to propose and vote on changes to the protocol by staking TEA tokens. Users who stake TEA tokens to projects delegate voting to that project.
Only projects that possess staked TEA tokens, stTEA, are eligible to vote on proposals or propose non-financial critical changes to the protocol.
## Why should I partake in the teaDAO
As a project maintainer partaking in the teaDAO allows you to play a central role in the development of the tea protocol. By staking TEA tokens, you gain voting power in the protocol’s governance, allowing you to propose and vote on changes. This active engagement fosters a sense of community and allows for the evolution of the protocol. Additionally, as an individual staking TEA on projects you support improves maintainability, bolsters its voting power, and provides incentives for contributors and maintainers.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tea.xyz/tea/i-want-to.../learn-about-the-teadao.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.