> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/dao/dao.md).

# Overview

The Decentraland DAO (Decentralized Autonomous Organization) is the governance body that manages and controls the Decentraland virtual world. It's composed of all MANA, LAND, and NAME token holders who can participate in the decision-making process.

This section provides a comprehensive overview of how the DAO operates, its capabilities, and how you can participate in governing Decentraland.

## Quick Links

* [Mission, Vision and Roles](/dao/dao/mission-vision-and-roles.md) - The DAO's approved mission and who is responsible for what
* [What is the DAO](/dao/dao/what-is-the-dao.md) - Introduction to the Decentraland DAO
* [How does the DAO work](/dao/dao/how-does-the-dao-work.md) - Understanding the governance mechanisms
* [What can you do with the DAO](/dao/dao/what-can-you-do-with-the-dao.md) - Actions and capabilities
* [Participation Requirements](/dao/dao/what-do-you-need-to-participate.md) - How to get involved
* [The DAO Fund](/dao/dao/the-dao-fund.md) - Treasury and funding
* [DAO Limitations](/dao/dao/the-daos-limitations.md) - Understanding boundaries
* [The DAO Smart Contracts](/dao/dao/what-smart-contracts-does-the-dao-control.md) - Technical infrastructure


---

# 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.decentraland.org/dao/dao.md?ask=<question>&goal=<user_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.
