> 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/treasury.md).

# Treasury

Treasury is the network's controlled asset layer. Revenue, budgets, vault releases, recalls, and proposal-driven spending remain traceable to an authorized source and destination.

## Current flow

* DAOBusiness revenue sweeps 100% to Treasury.
* Operating and project vaults receive explicit allocations.
* Founder operations are funded only by explicit, rail-checked Treasury allocations to the founder-fund vault; there is no automatic revenue percentage.
* Contract roles and proposal lanes determine who can register vaults, allocate budgets, release funds, recall funds, pause, or upgrade.

## Treasury proposals

The contract system has six treasury tiers. Each requires Contributors, Council, and Investors, with policy-set stakes, approval, quorum, voting duration, and cooling-off. A non-constitutional investor block may be overridden only when the contract's contributor supermajority and Council conditions are met.

## Dashboard requirements

The treasury view must show:

* confirmed balances and sync state;
* proposal category and required houses;
* registered vault hierarchy;
* allocation, release, recall, and pause status;
* policy limits and exact authorization required;
* transaction lifecycle and explorer evidence.

An application admin role never implies Treasury contract authority.


---

# 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/treasury.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.