> 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-june-13-2024.md). # Civics Meeting Minutes June 13, 2024 ### Constitutional Ratification Working Group Update * Ratification * Site visit #2 completed to Argentina to secure a venue for the Constitutional convention * Discussed constitutional workshop grants - 50 workshops will be selected, each with one delegate and one alternate. * An NFT series to accompany the constitutional ratification process this year is being planned * Drafting * Reviewed the topics discussed to date and remaining topics. Options will be drafted in preparation for Constitutional Workshops. ### Interim Constitutional Committee Election update * On track for interim constitutional committee member elections to open * Discussed some transition activities that could be helpful for the interim constitutional committee to prepare for the hard fork. --- # 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-june-13-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.