> For the complete documentation index, see [llms.txt](https://steeringcommittee.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://steeringcommittee.docs.intersectmbo.org/committee-meeting-notes/2026-meeting-notes/july-20-2026.md). # July 20 2026 ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | | ---------------------------------------------------- | ---------- | ----------------------------- | ----------------- | | [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N | | Jack Briggs | Yes | Executive Director | Y | | James Meidinger | Yes | Community Member Seat | Y | | Thiago Nunes | Yes | Community Member Seat | Y | | Kristijan Kowalsky | Yes | Community Member Seat | Y | | Jose Miguel de Gamboa | No | Community Member Seat | Y | | Sebastian Pabon | Yes | OSC Chair | Y | | Samuel Leathers | Yes | Product Chair | Y | | Martin Musagara | Yes | MCC Chair | Y | | Megan Hess | Yes | CBC Chair | Y | | Kevin Hammond | Yes | TSC Chair | Y | | Laura Mattiucci | No | GMC Chair | Y | | Nicolas Cerny | Yes | CCC Chair | Y | | Lorenzo Bruno | Yes | Head of Product & Membership | Y | | Larisa Mcfarlane | Yes | Head of Ecosystem & Community | Y | | Nick Cook | No | Head of Operations (Interim) | N | | Bosko Majdanac | Yes | Secretary of TSC | N | | Abhik Nag | Yes | Secretary of MCC | N | | Lloyd Duhon | Yes | Secretary of Budget Committee | N | | Terence McCutcheon | Yes | Secretary of OSC | N | | Lara Bonasorte | Yes | Secretary of GMC | N | | Thomas Lindseth | Yes | Secretary of CCC | N | ### Additional Attendees: Christian Taylor - Vice Chair of TSC Ken-Erik Ølmheim - Vice Chair of Civics Thyme Studio - Vice Chair of Product ## Agenda: * Committee Updates * CoC Process * ByLaws Voting * Committee Reward - Workshop * Committee Review Process * AOB ## Discussion/Actions ### 1. Opening & Agenda The meeting opened with confirmation of quorum and a review of the agenda. Topics included committee updates, review and approval of the draft Code of Conduct Process, preparations for the upcoming ISC and Board meeting, updates on the Bylaws Member Vote, and progress on the Committee Remit Review process. *** ## 2. Committee Updates * Technical Steering Committee (TSC) confirmed the successful enactment of the Van Rossum Hard Fork, with implementation progressing smoothly. The Committee Minimum Size governance action has also been enacted, reducing the Constitutional Committee minimum size from seven to five members. Work continues on governance actions to reduce the minimum pool cost and increase Plutus memory limits. Planning for the Dijkstra Hard Fork is underway, including discussions on scope, delivery timelines, and prioritisation of future protocol improvements. The committee also highlighted ongoing work relating to post-quantum cryptography and encouraged continued support for the TSC Treasury Withdrawal proposal. * Civics Committee shared an endorsement of governance improvement proposals relating to SPO voting and provided an update on the Constitutional Amendment Process (CAP) platform. The CAP portal is now hosted by Intersect and continues progressing towards public release, with members invited to test the platform while development continues. Discussion also covered how future constitutional changes should align with protocol development planning. * Budget Committee encouraged continued participation in the 2026 Budget Process Feedback Survey, noting that additional responses are needed to support future process improvements. The committee also advised that preparations are underway for administrative transition following the current committee secretary's departure. * Product Committee reported continued progress on onboarding approved Product Research Grant projects, with contract preparation ongoing. Committee representatives also continue participating in planning discussions for the Dijkstra Hard Fork. * Growth & Marketing Committee (GMC) continues developing strategic content to support DRep decision-making, including condensed research materials focused on ecosystem growth and adoption. The committee is coordinating with the Product Committee to avoid duplication of funded research and continues work on DeFi, agriculture, supply chain, governance adoption, and post-quantum positioning for Cardano. * Membership & Community Committee (MCC) and Open Source Committee (OSC) did not provide committee updates during this meeting. *** ## 3. Code of Conduct Process The ISC continued reviewing the draft Code of Conduct Process following comments received since the previous meeting. Discussion focused on: * Clarifying the scope of who may submit complaints. * Improving visibility of the complaint submission process through the Knowledge Base. * Ensuring complaints cannot be lost through operational improvements. * Handling potential misuse or malicious complaints while maintaining an accessible reporting process. * Clarifying that the review body provides recommendations, while formal disciplinary decisions remain subject to existing governance arrangements where required. #### Decision A formal motion was raised to approve the draft Code of Conduct Process, subject to the agreed comments and refinements being incorporated and the final version being presented for confirmation at the following meeting. The motion was approved unanimously by all voting members who participated in the vote. One voting member did not cast a vote. #### Next Steps * Incorporate the agreed amendments into the document. * Circulate the final version to the ISC for confirmation. * Complete the operational setup of the complaints process before publication, including access, notifications, and intake arrangements. *** ## 4. ISC & Board Meeting Preparation Members were reminded that the next ISC meeting will be the monthly session with the Board. To allow additional time for discussion: * The meeting duration has been extended to 90 minutes. * Regular committee updates will be omitted. * Members were encouraged to submit agenda items and questions in advance to maximise discussion time with the Board. Potential discussion topics included Board composition, governance matters, and updates on current organisational priorities. *** ## 5. Bylaws Member Vote An update was provided on the ongoing Bylaws Member Vote. Members were reminded to encourage participation within their committees and to explain that Enhanced KYC is required before voting, as this vote uses a higher level of identity verification than previous member verification processes. The importance of achieving the required participation threshold for adoption of the new bylaws was emphasised. *** ## 6. Committee Remit Review An update was provided on the Committee Remit Review initiative. Members were encouraged to continue participating in the Governance Working Group sessions, where work is ongoing to develop a structured process for reviewing committee remits before recommendations are presented to the Board. *** ## Actions & Next Steps * Finalise the agreed refinements to the Code of Conduct Process before publication. * Encourage committee members to participate in the ongoing Bylaws Member Vote. * Submit agenda items and discussion topics for the upcoming ISC and Board meeting. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://steeringcommittee.docs.intersectmbo.org/committee-meeting-notes/2026-meeting-notes/july-20-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.