> For the complete documentation index, see [llms.txt](https://docs.kuma.bond/kuma-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kuma.bond/kuma-protocol/dao-and-governance/proposal-framework/kuma-governance-proposal-kgp.md).

# KUMA Governance Proposal (KGP)

## 1. Writing a KGP

KGPs are about common governance proposals, especially the ones related to the treasury of the protocol and the DAO organization.

This type of proposal should include, in addition to all the points mentioned in the first part:

**Context:** (After summary)

Comprehensive overview of the proposal, treasury breakdown if needed.

The KGPs would concern but wouldn’t be limited to:

* Treasury allocation strategy & budgets
* Liquidity mining votes if any
* Grant program if any
* Contributors/Dao committees rewards
* Long term partnerships (i.e Dao Swaps)

## 2. Submission of proposal

KGPs concern the protocol treasury directly, which is why it might be best to define more conservative parameters than KIR ones:

* Admin: Team multisig
* Quorum: 0,25% of the total supply (2,5M MIMO)
* Voting duration: 5 days


---

# 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.kuma.bond/kuma-protocol/dao-and-governance/proposal-framework/kuma-governance-proposal-kgp.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.