Council and Board Framework
The Collective utilizes Councils and Boards that are comprised of community members. Councils and Boards may manage Collective resources or make decisions on behalf of tokenholders or Citizens, or fulfill roles otherwise filled by the Foundation. All Councils and Board play a temporary bootstrapping role in the Collective. The role of all Councils and Boards are intended to be progressively and programmatically reduced over time, as its functionalities are no longer needed or can be effectively managed by automated means.
The Foundation may authorize Councils or Boards aligned with the Collective Intents. All Councils and Boards must be accompanied by a Charter clearly outlining the responsibilities of members, the parameters around membership, and any associated budget. Any changes to the Charter must follow the same process for change that governs the Operating Manual.
To facilitate a constrained testing environment, participants in the initial iteration of a Council or Board may be determined via qualifying criteria or appointed by the Foundation, subject to ratification by Governance. After the initial term has ended, membership should be recalculated or renewed via a standard, open election process occurring on a regular basis as reasonably calibrated to the given role.
All Councils and Boards must have Leads. The Lead is always a non-voting member, so they remain focused on procedure and operations.
Councils and Boards will be authorized by the Foundation for an initial pilot period (at least one Season). After this pilot, Councils and Boards must be renewed by governance. After one Season of successful renewal, proof of concept Councils or Boards will become persistent in the Collective. Persistence is important as mature Councils and Boards may require non-trivial support, such as legal entities and multi-sig operations, as they become more autonomous within the Collective.
While persistent Councils and boards will be assumed to be renewed each Season, delegates may submit Dissolution Proposals if they believe a Council or Board is no longer fulfilling its mandate and should be discontinued. This should be determined by referencing the retrospectives published by Leads at the end of each Season and, increasingly, via data-driven analysis on the Council or Board’s contribution towards the target metrics under each Intent.
The current list of Councils and Boards in the Collective is detailed below, by type:
Persistent
- Grants Council
- Security Council
- Developer Advisory Board
Proof of Concept
- Milestone and Metrics Council
- Budget Board
All members may be removed from their position for failing to uphold the responsibilities outlined in the relevant Charter or for failing to act with honesty, integrity, and transparency. If there is a vote to remove a member, the Lead, or a simple majority of the remaining membership, may appoint a replacement for the remainder of the term.
Members may choose to step away from their role during the period between notice of a removal vote and the results of that vote. In the meantime, any non-voting Leads may temporarily fill a voting member’s role. If a Lead is removed, the same procedure applies, and an existing member elected by a simple majority of council members may temporary replace the Lead during this period. This temporary replacement may continue voting in their usual capacity during this short interim period.
If a member wishes to resign before the end of their term, they must appoint a replacement and communicate this change on the forum at least 7 days prior to this change taking effect.
Unless otherwise specified in a Charter, in the event any of the above action cause membership to fall below a pre-determined threshold, or to half of the original membership, operations will temporarily cease, or be transferred to the Foundation. In this case, the Foundation will facilitate a process with the community to assess the best way to proceed.
Members should only serve in one position per Season. There are no term limits for members, but they may be implemented in the future if the need arises.