> For the complete documentation index, see [llms.txt](https://docs.mangrove.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mangrove.exchange/governance/general-governance/governance-process/proposals.md).

# Proposals

Proposals are formalized and posted by Councils in the [proposals](https://forum.mangrove.exchange/c/governance/proposals/10) category of the Mangrove DAO forum. These proposals may originate from community-submitted ideas discussed in the [temp check](https://forum.mangrove.exchange/c/governance/temp-check/9) category or from the Councils themselves.

The structure of proposals mirrors that of the discussions in section 3.2, with the addition of a unique identifier. Proposals should include:

* **Header**: A unique ID constructed as ‘MIP’ followed by a chronological number (e.g., MIP1, MIP2), title, authors, date, and type (protocol or ecosystem).
* **Body**: As outlined in section 3.2, including summary, rationale, specification, and optional disclaimer and next steps.

Proposals must be submitted on the forum for comments and deliberation at least 5 days before any voting occurs. This period is crucial for participatory deliberation, allowing proposals to be refined and improved based on community feedback. Authors are required to make all edits visible, either through tracked changes or by adding subsequent posts, ensuring that any modifications to the original proposal are easily identifiable.


---

# 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.mangrove.exchange/governance/general-governance/governance-process/proposals.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.
