> For the complete documentation index, see [llms.txt](https://documentation.pulseap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pulseap.com/governance-and-community/governance-and-voting-power.md). # Governance & Voting Power Network upgrades don’t happen in a closed room. They happen on-chain, out in the open, with the community in control. If you hold $ePULSE, you can vote on proposals that shape the future of Pulse AP, whether it’s new features, protocol changes, or funding decisions. But we’re not here to recreate plutocracies. Voting power on Pulse AP isn’t just about how many tokens you hold. It’s also based on your usage, track record, and contributions. Your Perception Score plays a key role. That means no one gets to buy their way into control. Influence is earned through work, not wealth. Governance here is slower to game and more aligned with the spirit of decentralization. --- # 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://documentation.pulseap.com/governance-and-community/governance-and-voting-power.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.