> 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-24-2026.md). # August 24 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 | Yes | 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 | Yes | 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 Clarke | Yes | Head of Cardano Technology | N | | Bosko Majdanac | Yes | Secretary of TSC | N | | Abhik Nag | No | Secretary of MCC | N | | Terence McCutcheon | Yes | Secretary of OSC | N | | Lara Bonasorte | Yes | Secretary of GMC | N | | Thomas Lindseth | Yes | Secretary of CCC | N | ### Additional Attendees: Adam Rusch - Member of the Intersect Board Ken-Erik Ølmheim - Vice Chair of Civics Thyme Studio - Vice Chair of Product Christian Taylor - Vice Chair of TSC 8pro - Vice Chair of OSC Ian Hartwell - Observer ## Agenda: * Committee Update * Committee Review Process * Constitution Amendment Process Update * AOB ## Discussion/Actions ### 1. Committee Updates * Technical Steering Committee: The committee continued reviewing the proposed timeline for the Dijkstra hard fork, including the constitutional amendments required for new parameters. The current timeline targets an early December hard fork, although the schedule remains ambitious and clarification is being sought from IOG due to different versions of the delivery plan in circulation. The committee also discussed its budget items and the status of the minPoolCost governance action, where low SPO participation may prevent enactment. A dedicated technical and Constitutional Committee discussion on Dijkstra has been scheduled for August 28. * Open Source Committee: The committee continues work across the Maintainer and Tooling Sustainability programs, including onboarding two maintainers for the GovTool project and exploring support for projects such as Sila. The second round of the Developer Advocate Program is nearing completion, and the committee is looking to reactivate the Developer Experience Innovation Working Group to continue cross-ecosystem work on improving the Cardano developer experience. * Growth & Marketing Committee: Work continues on the DeFi and agriculture/supply-chain vertical approach. The committee reviewed a proposed list of 11 events for potential Cardano booth activations in 2027 and is reviewing applications for presentation slots at the Token2049 booth. Collaboration with the Product Committee is also continuing on mapping Cardano capabilities by vertical, with further work needed to define the approach and cadence between the two committees. * Civics Committee: The committee is reviewing phase two of the Constitution Amendment Process delivery and plans to approve an updated charter for the Governance Incentives Working Group. Work is also underway on a roadmap aligned with Cardano Vision 2030 and on increasing the visibility of governance through recurring community X Spaces. Concern remains around low participation in the Constitutional Committee update governance action ahead of the September 1 deadline, with additional community outreach planned. * Product Committee: The committee reviewed progress against milestones for ongoing product research and continues to monitor delivery. Committees that have not yet provided feedback on the Cardano 2030 KPI survey were reminded to do so. The Budget Committee confirmed that its feedback will be provided through a separate document rather than directly through the survey. * Membership & Community Committee: The committee launched its new working group, with the first session focused on planning. The working group will initially address member participation, recognition and inclusion, with an emphasis on understanding members' experiences. The committee is also consolidating member input on the Cardano 2030 survey and plans to submit its collective feedback. ### 2. Governance Participation The ISC discussed low SPO and DRep participation in current governance actions, particularly the Constitutional Committee update. Members noted that the votes received were largely supportive, suggesting that the primary issue may be participation rather than opposition. Possible contributing factors discussed included timing, voting tooling and user experience, lack of notifications, and the way non-participation is treated within the governance system. The possibility of changing ledger rules in the future so that SPO non-votes default to abstain rather than effectively counting against an action was raised, although such a change would require future ledger development and is not expected to be part of Dijkstra. The potential consequences of the Constitutional Committee update failing were also discussed. If the number of active Constitutional Committee members falls below the required threshold, treasury withdrawals would not be able to enact until sufficient committee membership is restored. ### 3. Committee Review Process An update was presented on the committee review work being developed through the Intersect Governance Working Group. The review consists of two related workstreams. The first focuses on committee effectiveness and ways of working. Data collection has started through a survey of current committee members and secretaries, with former members also expected to be invited. Survey findings will be supplemented by focus groups and interviews, with the aim of identifying characteristics of effective committees and developing recommendations that can help committees improve their ways of working. The second workstream focuses on committee remits and alignment with Intersect's current priorities. Existing committee remits will be reviewed against the goals and commitments contained in Intersect's approved budget to determine whether the current committee structure and scopes remain appropriate. The process is currently being designed and has not yet begun as a formal review of individual committees. The intention is to complete an initial outcome before the Annual Members Meeting where feasible, allowing any proposed remit changes to be considered for ratification. Members also discussed the importance of clearly distinguishing the advisory role of committees from responsibility for delivery and ensuring that any future structure provides committees with appropriate resources and clear objectives. ### 4. Constitution Amendment Process Update Five new submissions had been received through the Constitution Amendment Process during the previous week. Four were identified as attempted malicious content; the attempts failed and were reported internally. One valid new proposal suggested removing the immutable storage requirement for governance metadata on the basis that the relevant hash is already recorded on-chain. Additional comments had also been received on existing proposals. Committees were again encouraged to regularly review CAP submissions and provide feedback on proposals relevant to their areas of expertise. ### 5. Dijkstra and Constitutional Amendment Sequencing The ISC further discussed the relationship between the Dijkstra upgrade and the Constitution Amendment Process. The current approach is to keep the constitutional changes required for Dijkstra as focused as possible and not bundle them with unrelated constitutional amendments. The discussion indicated that the Dijkstra hard fork and its related constitutional amendment may be able to proceed as separate workstreams. Some constitutional guardrails depend on actual implementation performance, meaning final values may not be known until sufficient testing has taken place. Under the timeline discussed, the Dijkstra hard fork could occur first, followed by submission of the required constitutional amendment in early 2027. This sequencing remains subject to further technical and constitutional discussion. For broader constitutional changes, including proposals related to the Net Change Limit, members discussed a minimum process involving deliberation, preparation and communication, and on-chain voting. A realistic end-to-end constitutional amendment process was estimated at approximately six months, although preparatory work on future amendments could run in parallel. There was clear support for not bundling Dijkstra-related amendments with broader changes such as the NCL. Other constitutional proposals can continue through deliberation and potentially be ready to progress once the Dijkstra-related constitutional work has been completed. ### 6. Actions & Next Steps * Committee chairs, vice chairs and secretaries to share the committee effectiveness survey with current committee members. * Committee members to review the proposed committee remit review process and provide comments and suggestions on the working document. --- # 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-24-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.