> For the complete documentation index, see [llms.txt](https://docs.hatom.com/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatom.com/getting-started/governance/introduction.md). # Introduction Hatom's on-chain **Governance** deploys a mechanism that empowers holders of the [**"HTM Token"**](/getting-started/learn-more-about-hatom-token/introduction.md) to cast votes for protocol changes directly on the blockchain. This system was designed to afford individual users greater influence in the **Governance** process. Under this structure, **Governance** proposals are disseminated among the community through polls and, upon securing the requisite votes for ratification, are subsequently executed. On-chain **Governance** mechanisms are widely employed across DeFi platforms. To earn voting rights or the ability to make a proposal, you typically must hold a specified quantity of HTM tokens. The **Hatom Protocol Team** consistently gathers feedback, which is used to create tailored polls that align with the community's needs and preferences, allowing for continual App upgrades. Once the polls are assembled and displayed in the voting section within the [**"App"**](https://devnet.hatom.com/governance), the community is granted a period of 2-3 days to cast their votes and determine whether the proposed features should be implemented. If the votes yield a favorable outcome, the proposed feature will be integrated into the **Hatom Protocol** in the ensuing days, reflecting the community's active participation in shaping the platform's development. --- # 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.hatom.com/getting-started/governance/introduction.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.