> For the complete documentation index, see [llms.txt](https://docs.chainguardians.io/cgdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chainguardians.io/cgdao/council-and-treasury-frameworks/overview.md).

# Overview

DAO Committee - 3 of 5 threshold multi-sig safe. (Idon, Robbeh, Emma, IamTroll, Guardian Board) 

Guardian Board - 3 of 4 threshold multi-sig safe. (Adam, Magnus, IamTroll, Mridul) (eventually, it will have 8 members with a 5 of 8 threshold) 

Operating DAO Treasury – 3 of 3 threshold multi-sig safe (Idon, Emma, Robbeh) 

Community DAO Treasury – controlled by DAO Committee multi-sig safe. 

Security Treasury – controlled by the Guardian Board’s multi-sig safe.

### Councils

{% tabs %}
{% tab title="cgDAO Committee" %}

| Name           |       Position       | Vote Power |
| -------------- | :------------------: | :--------: |
| Robbeh         |        Founder       |   1 Vote   |
| Emma           |        Founder       |   1 Vote   |
| Idon           |   Founder/Treasury   |   1 Vote   |
| IamTroll       | Governance Architect |   1 Vote   |
| Guardian Board |       Security       |   1 Vote   |
| {% endtab %}   |                      |            |

{% tab title="Guardian Board" %}

<table><thead><tr><th width="227.00533204071743">Name</th><th width="287.66666666666663" align="center">Position</th><th align="center">Vote Power</th></tr></thead><tbody><tr><td>Adam</td><td align="center">Full Stack Dev</td><td align="center">1 Vote</td></tr><tr><td>Magnus</td><td align="center">Solidity Expert</td><td align="center">1 Vote</td></tr><tr><td>Mridul</td><td align="center">Security and Backend Specialist</td><td align="center">1 Vote</td></tr><tr><td>IamTroll</td><td align="center">Community liaison</td><td align="center">1 Vote</td></tr><tr><td>Community Member</td><td align="center">N/A</td><td align="center">1 Vote</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

### Treasury

{% tabs %}
{% tab title="Community Treasury" %}

| Name           |     Position    |
| -------------- | :-------------: |
| Idon           |  Founder/Admin  |
| Emma           |  Founder/Admin  |
| Robbeh         |  Founder/Admin  |
| IamTroll       | Architect/Admin |
| Guardian Board |     Security    |
| {% endtab %}   |                 |

{% tab title="Operating Treasury" %}

| Name         |    Position   |
| ------------ | :-----------: |
| Idon         | Founder/Admin |
| Emma         | Founder/Admin |
| Robbeh       | Founder/Admin |
| {% endtab %} |               |

{% tab title="Security Treasury" %}

| Name             |    Position    |
| ---------------- | :------------: |
| Adam             |   Lead/Admin   |
| Magnus           | Security/Admin |
| Mridul           |  Backend/Admin |
| IamTroll         |    PM/Admin    |
| Community Member |       N/A      |
| {% endtab %}     |                |
| {% endtabs %}    |                |


---

# 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.chainguardians.io/cgdao/council-and-treasury-frameworks/overview.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.