> 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-10-2026.md). # August 10 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 | No | MCC Chair | Y | | Megan Hess | Yes | CBC Chair | Y | | Kevin Hammond | No | TSC Chair | Y | | Laura Mattiucci | No | GMC Chair | Y | | Nicolas Cerny | Yes | CCC Chair | Y | | Lorenzo Bruno | No | Head of Product & Membership | Y | | Larisa Mcfarlane | No | 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: 10.08.2026 * Committee Update * ByLaws Voting * Cardano Vision KPI SUrvey * AOB ## Discussion/Actions ### 1. Committee Updates Civics Committee: The Constitution Amendment Process (CAP) portal is live in alpha and has already received several submissions. The committee is also working with IOG on a proposal to reimburse Constitutional Committee members for eligible setup-related costs, including hardware, legal consultation, and establishment of legal entities. The Constitutional Committee governance actions are currently live, with SPO participation identified as an area to monitor. Growth and Marketing Committee: Activity was limited during the previous week due to summer availability. The committee's next meeting will focus on reviewing the vertical approach for the Product Committee and receiving an update on the agriculture vertical. Open Source Committee: The Maintainer Program is operating at full speed, with close to 20 projects participating and maintainers assigned across them. The tooling program is also active, supporting a range of core and community projects, with further updates expected as the programs progress. Technical SteeringCommittee: The committee discussed enacted budget allocations, including which approved project funds would be converted to stable and which would remain in ADA. Discussions also covered governance actions related to execution cost reduction and Plutus memory limit increases, the Product Committee survey, and potentially introducing post-quantum cryptography as a standing topic. Current attention remains primarily focused on Dijkstra and related scope, questions, and feedback. ### 2. Intersect 2026 Roadmap An overview of Intersect's priorities for the remainder of 2026 was presented. Key areas include the upcoming Board elections, the Constitution Amendment Process, the Dijkstra upgrade, committee review and evolution, technical stewardship of core repositories, security and incident response, committee and working group coordination, and administration services. The Board election process is expected to begin shortly, with two elected Board seats planned for September. Committee structures are also being reviewed, with any proposed changes expected to require ratification at the Annual Members Meeting later in the year. Technical stewardship of core repositories continues to transition to Intersect, with Mithril already moved and additional core repositories expected to follow. This transition will also require further consideration of repository governance, product roadmaps, release management, and coordination between multiple delivery partners. Nick Clark has joined Intersect as Director of Cardano Technology, with an initial focus on the Dijkstra upgrade and strengthening security and incident response capabilities. ### 3. Dijkstra Upgrade The Dijkstra upgrade remains one of the primary delivery priorities for the remainder of 2026. The current plan targets pre-release nodes during October, a final node version in early November, and a hard fork in early December. The timeline was acknowledged as ambitious and dependent on successful testing through preview and pre-production environments. Particular attention will be required to ensure sufficient SPO awareness and participation ahead of the hard fork. The roadmap is closely connected to the Constitution Amendment Process, as the Constitution must contain the necessary guardrails and technical provisions to support Dijkstra. The minimum priority for the CAP process is therefore to ensure that the Constitution is ready for the Dijakstra upgrade. ### 5. LayerZero and Pentad An update was provided on the LayerZero integration. Although work experienced an approximately six-week delay due to LayerZero prioritizing security-related matters, the original target of completing the integration by the end of 2026 remains unchanged. A more detailed communication update is being prepared. The group also discussed the impact of EMURGO stepping away from the Pentad. No immediate operational gap was identified, as ongoing execution and administration activities are already being handled by Intersect and IOG. However, members acknowledged that the Pentad's longer-term governance structure may need to evolve, potentially including broader membership and more formal participation arrangements. ### 6. Cardano 2030 KPI Survey The purpose of the Product Committee's KPI survey was clarified. The exercise is intended to review the existing Cardano 2030 KPIs and assess how well they reflect the work and responsibilities of the different committees. Committees are encouraged to review the existing KPIs collectively and identify areas where their work is not adequately represented. It was acknowledged that some committees provide enabling or governance functions that may not translate directly into numerical KPIs, and this can also be reflected through the survey. ### 7. Constitution Amendment Process The CAP portal is now operational and had already received three proposals and an issue statement at the time of the meeting. Committees were encouraged to regularly review submissions relevant to their areas of expertise and provide feedback where appropriate. The group discussed the importance of ensuring sufficient time for community deliberation and review of proposed amendments. A 30-day deliberation period was discussed as an appropriate minimum for proposals progressing through the process. Given the importance of constitutional amendments and the number of proposals expected, the group supported adding a recurring CAP update to future ISC meetings. A short standing agenda item will be used to review new proposals, their progress, and any areas requiring committee input. ### 8. Constitutional Amendments for Dijkstra The group discussed how amendments required for the Dijkstra upgrade should be handled alongside other proposals emerging through the CAP process. There was agreement that amendments necessary to enable Dijakstra should be treated separately and prioritized ahead of unrelated constitutional changes. This is intended to reduce complexity and ensure that technical changes required for the upgrade are not put at risk by being bundled with broader constitutional amendments. Other CAP proposals can continue through the process independently and be considered separately after the Dijakstra-related constitutional requirements have been addressed. ### 9. Board Update An update was provided following EMURGO's resignation from Intersect and its Board seat. EMURGO will not appoint a replacement, leaving the position vacant. The Board is considering whether to appoint someone to serve the remainder of the term, as permitted under the Bylaws. Input Output Group has expressed interest in continuing as a sustaining member when its current term ends, while the Cardano Foundation has also expressed interest in a sustaining membership position. Discussions are ongoing regarding the University of Wyoming's sustaining membership and its potential continuation through the College of Law. The current seven-member Board structure was discussed and considered to provide an effective balance between sustaining member representation and membership-elected Board members. ### 10. Actions & Next Steps * Add a 5–10 minute Constitution Amendment Process update as a standing agenda item for future ISC weekly meetings. --- # 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-10-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.