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

# Governance

## Principles

1. **Tax cannot be rerouted.** 3% goes to the blackhole only.
2. **Supply cannot be minted.** No `mint` on the contract.
3. **Treasury is visible.** If an ops multisig exists, the address is public and spends carry a proposal ID.
4. **Slow, then fast.** Early multisig covers emergency pause. After stability, hand over or burn upgrade keys.

## Council (early)

| Role                     | Duty                                                                 |
| ------------------------ | -------------------------------------------------------------------- |
| Holders                  | Vote, delegate, submit proposals (if they meet the threshold)        |
| COSM official / multisig | Execute passed proposals, coordinate launch windows, emergency pause |
| Builders                 | Take missions or grants, ship public goods                           |

## Proposal types

* **Ecosystem:** collabs with later COSM launches, prairie mission seasons
* **Parameters:** badge thresholds, display rules (tax rate and blackhole destination are out of scope)
* **Catalog:** integrations, sunsetting an experiment
* **Charter amendments:** higher pass rate, longer vote

## Suggested vote params

Changeable by proposal:

* Vote window: 5 Earth days
* Pass: simple majority, quorum 2% of circulating
* Charter amendment: 2/3 majority, quorum 5%

{% hint style="info" %}
The 3% tax and “100% of tax burned” are flagship spec, not routine governance knobs.
{% endhint %}


---

# 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://doc.niulai.app/governance.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.