> 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-february-8-2024.md). # Civics Meeting Minutes February 8, 2024 ### Review of Activities since last meeting * Comments on the interim constitution * Preparing for the integrated Cardano ecosystem workshop Feb 19/20. ### The committee discussed the integrated Cardano ecosystem workshop * The focus is on process design for the vision and open source product backlog, and will capture questions about Intersect governance as they surface. ### Intersect Governance and Cardano Civics Committee governance * There was discussion about clarifying the remit of this committee and whether it should cover the governance of Intersect, or if it might be a separate group dedicated to defining and implementing the committee governance standards * Intersect governance needs highlighted in the meeting included: * Process for the members to establish committees and working groups * RACI and charters across committee to clarify remits and how they work together * Representation: when is a member representing Intersect, member affiliation, recusal, code of conduct * It was noted that the Community Advisory Board consisting of members has been established and is starting to advise on these standards, starting with the board election process, then working down to committees. * This committee wants to better define its processes - when and how to vote, how to increase transparency, improved charter. --- # 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-february-8-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.