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

# Proposals

Proposals carry executable calldata and a category that determines sponsorship, houses, voting policy, and cooling-off requirements.

## Proposal flow

1. An eligible member proposes a description, target, value, and action.
2. The contract validates the category and execution target before accepting the proposal.
3. The authorized snapshot service commits voter eligibility and denominators.
4. Contributors and investors cast snapshot-proven votes where required; Council members consent or submit reasoned objections.
5. Anyone may finalize after the voting window.
6. A passed proposal waits through its cooling-off period.
7. Anyone may execute; the call originates from Governance and must still satisfy the target contract's authorization.

## Categories

Treasury tiers require all three houses. Standard, critical, judicial, and emergency lanes require Contributors and Council. Constitutional changes require all three and use entrenched minimum approval, duration, and cooling-off rules.

## Terminal states

A proposal may be rejected, executed, cancelled through an explicit founder lane, or withdrawn by its proposer before a snapshot opens. Stakes refund once on terminal settlement according to the contract rules.

{% hint style="info" %}
The dashboard shows the category, required houses, snapshot status, deadline, tallies, cooling-off period, execution state, and cancellation reason. See [Developer Overview](/developers/developers.md) for feature availability.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.builtbydao.com/governance/proposals.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.