> 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-april-25-2024.md). # Civics Meeting Minutes April 25, 2024 ### Interim CC selection process * Reviewed the key skills for Constitutional Committee members - operating model, managing keys, constitutional review and deliberation, voting on the governance actions and managing communications * Reviewed a proposed selection process for the interim constitutional committee that includes an application process. ### Interim constitution go-live schedule * Reviewed the steps needed before the interim constitution goes live, as well as the steps to get it integrated into the Chang hard fork ### Constitutional Ratification Working group update * Constitution drafting activities have focused on reviewing the tenets (akin to rights in the community), as well as a gap analysis of the interim constituiton’s articles to highlight areas for change ### Committee info request * Discussed the request to add more information about the civics committee to the Intersect Knowledge base and agreed to publish all consenting member’s names and a contact email address for the committee --- # 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-april-25-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.