> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/4.-product-organization-and-ecosystem-design/4.5-governance-voting-system.md).
# 4.5 Governance Voting System
A DAO-based governance system empowers GET holders to participate in shaping project directions.
**Voting Topics Include:**
* Selection of projects to support (artists, films, events, etc.)
* Performer selection, venue and contents policy decisions
* Approval or disapproval of staking fees and partnership deals
* Proposals for new platform features
**Voting mechanism:**
* 1 GET = 1 vote (influence based on amount held)
* Conditional voting (Under staking only, NFT holders only, etc.)
* Incentives for participants (e.g., limited NFT, GET Miles)
* Proposers are required to have a certain amount of GETs and disclose information
---
# 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.global-entertainment-token.org/4.-product-organization-and-ecosystem-design/4.5-governance-voting-system.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.