> 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-october-17-2024.md). # Civics Meeting Minutes October 17, 2024 Governance support working group update - 2025 objectives and budget review * Reviewed the line items proposed in each of the Governance Support budget buckets * Discussed the process for budget approval Hard Fork Working Group (HFWG) Request * The HFWG requested the CCC’s input as to whether a minimum threshold of DRep stake is needed for the next hard fork. * The CCC discussed the topic, scenarios of concern, and the historical debate on the subject. Both long term and short term concerns were discussed, and the general sentiment was that the short term concerns do not merit defining a minimum threshold of DRep stake, but innovation will be important long-term to ensure delegation to DReps works as-intended. * It was also discussed that the Interim Constitutional Committee’s role is in the constitutionality of a hard fork. The constitution requires considering the technical guidance of experts as required in the guardrails, but there’s no constitutional requirement for a certain DRep threshold. * The CCC will document their opinion and share it back with the HFWG. Progress update: Constitution Ratification WG * Interest in getting the ICC’s input on the constitution draft, potentially as a workshop to get their thoughts. --- # 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-october-17-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.