> 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/governance-process/voting/elections.md).

# Elections

## **Election Day**

As each proposal passes, the community will get closer to [**voting milestones**](#voting-milestones) and an eventual community election day.&#x20;

The [**Guardian Board**](/cgdao/council-and-treasury-frameworks/councils/cgdao-guardian-board.md) will unlock a seat for community elections when certain milestones are crossed. This aims to bring the GB closer to a more community-weighted panel. The GB will start with 4 internal team members and gradually open 4 seats for community members.&#x20;

This is meant to allow direct community participation from within the DAO organization. As the GB seats are filled, the community gains more power within the GB and also the [**DAO Committee**](/cgdao/council-and-treasury-frameworks/councils/cgdao-committee.md), as the GB itself is a member of the DAO Committee.

## Voting Milestones&#x20;

{% hint style="success" %}

1. **First election** = 5 passed proposal&#x20;
2. **Second election** = 25 passed proposals&#x20;
3. **Third election** = 50 passed proposals&#x20;
4. **Fourth election** = 100 passed proposals&#x20;
5. **Ascended Guardian election** = 150 passed proposals
   {% endhint %}

## Election Process&#x20;

After voting milestones have been met, the following week will be used for candidates to campaign for a seat on the Guardian Board. If warranted, some candidates can be nominated outside of Discussion posts. The DAO Committee and Guardian Board members are not allowed to vote on candidates. When officially granted the position, a user must join the Guardian Board multi-sig safe as a part owner.

1. Candidates will create a post in the Discussion area of the Forum to “pitch” themselves to the community.
2. After the week of campaigning ends, 3-4 candidates will be chosen for a multi-choice Snapshot vote, based on discussion and community engagement/activity on the Forum.&#x20;
3. The voting period will last 4 days and grant the candidate a seat on Guardian Board if passed.
4. In certain cases, [**ELECT**](/cgdao/governance-process/proposals/proposal-tags.md) proposals might need to be escalated to another vote prior to a Governance level Vote.

## Ascended Guardian&#x20;

After all 4 Guardian Board seats have been filled, a new DAO Committee member seat will be unlocked. This member will be elected by the GB board from the community. Elected GB members are also eligible for the position and would be some of the best candidates.&#x20;

If elected from the GB, then an election for that seat will need to be held to replace that member.&#x20;

{% hint style="info" %} <mark style="color:blue;">**Important:**</mark> All elected officials will be subject to a 6 month term before their seats next election.
{% 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 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/governance-process/voting/elections.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.
