> 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/august-3-2026.md). # August 3 2026 ## Attendees: | Name | Attendance | Role | Voting Seat (Y/N) | | ---------------------------------------------------- | ---------- | ----------------------------- | ----------------- | | [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N | | Jack Briggs | No | 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 | No | TSC Chair | Y | | Laura Mattiucci | No | GMC Chair | Y | | Nicolas Cerny | No | 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 | | Terence McCutcheon | Yes | Secretary of OSC | N | | Lara Bonasorte | No | 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 8pro - Vice Chair of OSC Selin Rhayem - Observer ## Agenda: 03.08.2026 * Committee Update * ByLaws Voting * Cardano Vision KPI SUrvey * AOB ## Discussion/Actions ### 1. Opening & Agenda The meeting opened with confirmation of quorum and a review of the agenda. The primary topics included committee updates, the outcome of the Bylaws Member Vote, and the launch of the Cardano Vision 2030 KPI Framework review. *** ### 2. Committee Updates * Product Committee reported continued progress on the Product Research Programme, refinement of the Dijkstra Hard Fork scope in collaboration with engineering teams, and preparation of public planning documentation for both the hard fork and product roadmap. The committee also introduced a new KPI review survey for committees. * Budget Committee reported that the transition to a new committee secretary has been completed smoothly. The committee reviewed responses received through the Budget Process Feedback Survey and agreed to extend the survey while undertaking targeted outreach to DReps, vendors, and other stakeholders to increase participation before beginning work on recommendations for the next budget cycle. * Civics Committee provided a brief update, noting continued progress on the Constitutional Amendment Process (CAP) alpha platform and work by the Governance Incentives Working Group, including discussion of a potential Treasury Withdrawal proposal to support future activities. * Membership & Community Committee (MCC) reported on a successful community office hours session that generated valuable discussion and feedback from members. The committee is finalising its working groups and priorities and will shortly announce the onboarding of an additional committee member. * Open Source Committee (OSC) announced the launch of the second cohort of the Maintainer Retainer Programme, supporting 21 maintainers across 14 projects. The committee highlighted that the programme aligns with similar initiatives across the wider open-source ecosystem and strengthens the sustainability and competitiveness of Cardano's open-source development. * Technical Steering Committee (TSC) reported there were no significant updates since the previous meeting. * Growth & Marketing Committee (GMC) did not provide an update during this meeting. *** ### 3. Bylaws Member Vote An update was provided on the recently completed Bylaws Member Vote. The proposed bylaw amendments were approved, with: * 47 members participating * 44 votes in favour * 3 abstentions The updated bylaws will be published in the Knowledge Base following final review. It was also noted that members who completed the enhanced KYC process during the bylaw vote will already be eligible to participate in the upcoming Board election, with further communication planned to encourage additional members to complete the required verification before voting opens. *** ### 5. Cardano Vision 2030 KPI Framework The Product Committee introduced a committee survey to review the Cardano Vision 2030 KPI Framework. Each committee has been asked to complete a single survey collaboratively, providing feedback on: * The relevance of the current KPIs to their committee's remit. * Potential improvements or additions to the KPI framework. * Any recommendations for refining the existing measures. Committee Chairs, Vice-Chairs, and Secretaries will receive the survey, with responses requested during August. Feedback will be reviewed by the Product Committee before considering updates to the framework. *** ### Actions & Next Steps * Publish the updated Intersect Bylaws in the Knowledge Base. * Committees to complete the Cardano Vision 2030 KPI Framework survey during August. --- # 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/august-3-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.