> For the complete documentation index, see [llms.txt](https://docs.ambient.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ambient.finance/concepts/governance-and-policy.md).

# Governance & Policy

Ambient protocol uses a three-layer division of responsibility:

![](/files/smsyh165lG9a8UC8R4eD)

**Governance** fills the traditional role of a DAO. It includes full power over the protocol, and is controlled by M-of-N multisigs and timelock resolutions.

**Policy** is an intermediate layer that sits between the DAO governance and the DEX contract itself. It can ether directly relay resolutions from the governance layer, or delegate limited administrative control of the DEX to external smart contract *policy oracles* explicitly installed by DAO governance.

 **Mechanism** is the underlying DEX contract itself. `CrocSwapDex` (the core smart contract holding dex liquidity and positions) is built with tunable parameters that can be dynamically adjusted by external policy oracles. That allows the protocol to improve and experiment with new functionality in a way that's safer and more contained than directly upgrading the underlying DEX smart contract. 


---

# 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.ambient.finance/concepts/governance-and-policy.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.