> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-civics-committee/meeting-minutes/2024-civics-meeting-minutes/civics-meeting-minutes-may-23-2024.md). # Civics Meeting Minutes May 23, 2024 ### Interim CC Election Process * Discussed the interim constitutional committee election process and tradeoffs of several options. * Motion: Intersect will provide the platform for the interim constitutional committee election. The candidacy is open to anyone as long as they can register on the Summon voting tool. It’s a two stage system. 1) Register intent to run. 2) Voters will select the top 3 candidates using their stake as weight. The Summon platform will calculate the top 3 candidates by stake weight. Post election, resources, training, and infrastructural improvements will be provided to the winners (as-needed). The interim CC term is 73 epochs following the first Chang hard fork. * Passed unanimously with one abstain (recusal). ### Progress update from Drafting Task Force * Drafting has focused so far on principles and tenets, with outstanding topics identified to progress the draft. * Discussed an in-person drafting workshop in late July. ### Progress update from Ratification Task Force * Supported the Intersect grant process to allow grants for Constitutional workshops to open. * Next focus will be defining the remaining workshop details and open questions on constitutional delegates. ### Workshop grants evaluation * Discussed the Intersect grant process and how it uses relevant committees to support evaluation. All except 1 CCC member must recuse themself from evaluating, so other evaluators will be recruited from Intersect membership. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://committees.docs.intersectmbo.org/intersect-civics-committee/meeting-minutes/2024-civics-meeting-minutes/civics-meeting-minutes-may-23-2024.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.