> 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/baum-deed-deck/traits.md).

# Sub-DAOs, traits and the Multiplier Attribute

Sub-DAO assignment, the seven traits, and the one trait with a mechanical effect.

## Sub-DAO membership

Each Broker is assigned at claim — at random and with equal weight — to one of **five sub-DAOs**. Each sub-DAO is an asset class. **Stocks** is the first; the other four are named at reveal. See [Sub-DAOs](/network/sub-daos.md).

## Traits

Every Broker carries seven traits:

1. Background
2. Body
3. Hair
4. Eyewear
5. Prop
6. Outfit
7. Multiplier Attribute

A Broker's rarity comes from its whole trait set, and a rare Broker's premium is what collectors pay for those traits.

Every Broker is a playing card in the Deed Deck. Art and traits are revealed the week of **September 28**.

## Multiplier Attribute

The Multiplier Attribute is the one trait with a mechanical effect: **it multiplies the points the Broker earns, and nothing else.** It does not change reward weight, allocations, or governance.

| Multiplier Attribute | Share (base odds) | Points multiplier |
| -------------------- | ----------------- | ----------------- |
| Common               | \~85%             | ×1.00             |
| Uncommon             | \~12%             | ×1.25             |
| Rare                 | \~3%              | ×1.50             |

A lucky roll climbs the levels faster, but every Broker can reach Level 5. The multiplier is applied after the daily points cap — see [Earning points](/points-and-levels/points-and-levels.md#daily-cap).

Reserving 3 or 5 Brokers in one commit improves these odds — see [Mint](/baum-deed-deck/mint.md#reserving-in-quantity).


---

# 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/baum-deed-deck/traits.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.