> 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-january-18-2024.md). # Civics Meeting Minutes January 18, 2024 ### Governance Guardrails Working Group updates * The committee updated the wording of the treasury withdrawal guardrails. They now read: * DReps shall define a net change limit for the Cardano Treasury’s balance per period of time. The budget for the Cardano Treasury must not exceed the net change limit for the Cardano Treasury’s balance per period of time. Treasury withdrawals must not be ratified until there is a community-approved Cardano budget then in effect pursuant to a previous on-chain governance action agreed by the DReps with a threshold of greater than 50% of the active voting stake. * The first complete version of the Interim constitution, the bulk of which is the guardrails, was discussed and comments requested from the Civics Committee by Jan 26th. ### Informational update about the DRep Code of Conduct work * The community process to define the DRep code of conduct was presented. 5 community workshops will continue to review the code of conduct, which is now drafted as a detailed text document, as well as a graphical version. * A new key rotation scheme CIP is being drafted, which can be explored as a mechanism to enforce the DRep code of conduct. * The committee seconded a motion to create a working group for a DRep code of conduct, with at least 4 members in support. ### Committee governance * The committee discussed wanting greater transparency with Intersect, needing to establish several committee governance processes --- # 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-january-18-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.