> For the complete documentation index, see [llms.txt](https://docs.alphadune.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphadune.com/alpha-dune-governance/introduction.md).

# Introduction

Alpha Dune Governance is the process of collective decision-making and management of the Alpha Dune Network. Alpha Dune Governance involves various stakeholders, such as DUNE token holders, delegates, guardians, non-token holders, and the Alpha Dune Company, who have different rights and responsibilities in the governance hierarchy. 

Alpha Dune Governance aims to ensure the security, reliability, and innovation of the network, as well as the alignment of the network’s vision and mission with the interests and values of the community. 

Alpha Dune DAO is a decentralized collective that aims to create the ultimate gaming chain for web3 gaming applications and is based on the principles of transparency, accountability, and participation.

Stakeholder overview Alpha Dune DAO consists of the following categories:

1. Token holders
2. Delegates
3. Guardians
4. Non-token holders
5. Alpha Dune company

### DAO Toolkit

* Snapshot (coming soon)
* Forum (coming soon)


---

# 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.alphadune.com/alpha-dune-governance/introduction.md?ask=<question>&goal=<endgoal>
```

`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.