> 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/2025-civics-meeting-minutes/civics-meeting-minutes-january-09-2025.md). # Civics Meeting Minutes January 09, 2025 Chair election * Quorum of 75% not met. Agreed to hold an asynchronous voting process to elect the chair. Ratification Working Group (WG) Updates * Drafting of the Constitution Governance Action is underway and undergoing reviews of the documentation and formatting. * Activities to pull together content that supports the constitution ratification are well underway, as well as coordinating communications to disseminate those educational materials. * The committee discussed a backup plan for if the Plomin Hard Fork is not enacted by Jan 31, 2025. This plan will be formally documented and put to full vote of the Civics Committee to formally instruct Intersect of this plan. * The platform and process for “Voltaire Papers” was discussed. This will be a repository to hold papers that provide education, context, and perspectives of people who were part of the drafting process. * The Constitutional Delegates are working on a set of papers to contribute their perspectives. --- # 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/2025-civics-meeting-minutes/civics-meeting-minutes-january-09-2025.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.