> For the complete documentation index, see [llms.txt](https://docs.baumai.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baumai.xyz/network/sub-daos.md).

# Sub-DAOs

Five asset-class sub-DAOs, each with its own USDX-paired token.

There are five sub-DAOs. Each is an asset class, and every Broker belongs to exactly one — assigned at claim, at random and with equal weight (see [Sub-DAO membership](/baum-deed-deck/traits.md#sub-dao-membership)).

Each sub-DAO launches its own token on the Baum launchpad. **Sub-DAO tokens pair only with USDX.**

## Token allocation

Per sub-DAO:

| Allocation              | %   |
| ----------------------- | --- |
| LP / USDX               | 40% |
| Baum treasury           | 20% |
| Brokers of that sub-DAO | 20% |
| Brokers of all sub-DAOs | 10% |
| That sub-DAO's treasury | 10% |

Both Broker allocations **stream over 12 months**, recomputed each epoch by [reward weight](/points-and-levels/levels.md) and votes cast. The 10% cross-sub-DAO slice is weighted by reward weight and governance participation across the network. The Multiplier Attribute plays no part in either.

Each sub-DAO's LP bucket follows the same [LP-out ladder](/tokens/treasury-lp-out-ladder.md) as BAUM, funding its treasury as the token grows. The remaining 25% stays as standing USDX liquidity.

## Launch order

* **Stocks** launches first, in **October**.
* The second sub-DAO follows four to six weeks later.
* Then one every four to six weeks.


---

# 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.baumai.xyz/network/sub-daos.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.