> 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-steering-committee/committee-meeting-notes/2026-meeting-notes/june-8-2026.md). # June 8 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 | Yes | Community Member Seat | Y | |


| No | 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 | |


| 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: Rand McHenry - Member of the Board Ken-Erik Ølmheim - Vice Chair of Civics Fred Tanaka - Observer Selin Rhayem - Observer ## Agenda: * Committee Updates * ISC Actions * Committee Reward Review Progress Update * ByLaws Voting * Q2 Events * AOB ## Discussion/Actions ### 1. Opening & Agenda The meeting opened with attendance confirmation and a review of the agenda. Topics included committee updates, ISC action tracking, committee rewards, bylaw voting preparations, and upcoming Q2 planning activities. *** ### 2. Committee Updates * Civics Committee confirmed completion of its Chair and Vice-Chair elections, with Nicolas Cerny re-elected as Chair and Ken-Erik Ølmheim elected as Vice-Chair. The committee also extended the Constitutional Committee election application period due to low candidate numbers and is supporting outreach efforts to encourage additional applicants. Discussions also included potential collaboration with the Minimal Viable Governance team on governance improvements. * Growth & Marketing Committee (GMC) reported strong engagement from newly elected members, who are currently reviewing the committee framework and priorities. The committee completed a coordinated review of marketing and growth-related budget proposals and submitted consolidated feedback through the Hydra platform. * Open Source Committee (OSC) continues to focus on its budget proposal and related community engagement efforts. The committee highlighted the importance of broader ecosystem support and feedback as proposal review progresses. * Budget Committee confirmed its new leadership, with Megan Hess elected as Chair and Kristijan Kowalsky as Vice-Chair. The committee is reviewing priorities for the remainder of the year while monitoring proposal voting progress. Members also noted that Hydra participation has reached nearly 3 billion ADA and discussed potential Net Change Limit implications for proposals moving to the on-chain stage. * Technical Steering Committee (TSC) reported progress toward the upcoming hard fork, including completion of the Constitutional Committee minimum size governance action and ongoing readiness reviews. A final go/no-go decision is expected following additional testing and validation activities. The committee also discussed feedback from members regarding recent governance process changes. * Product Committee confirmed election of a new Vice-Chair and continues evaluating submissions received through the Product Research Grants initiative. The committee is reviewing proposals, engaging with DReps on feedback received through Hydra, and highlighted its recent decision to return approximately 100,000 ADA in unused funds to the treasury. * Membership & Community Committee (MCC) completed its leadership elections, with Martin elected as Chair and Sanjaya continuing as Vice-Chair. *** ### 3. ISC Actions & Governance Work An update was provided on outstanding ISC action items. Key updates included: * The Code of Conduct Working Group kickoff meeting has been scheduled. * Discussions continue regarding expansion of independent audit activities and contract oversight mechanisms. * Intersect is engaging an independent third-party auditor to review activities associated with the Critical Integrations governance process. * Ongoing work continues to improve committee reporting, action tracking, and governance transparency. Additional discussion explored the structure and accountability of the Pentad, including future opportunities to improve transparency, community representation, and governance maturity as the initiative evolves. *** ### 4. Committee Rewards Policy An update was provided on the ongoing review of the Committee Rewards Policy. The working group responsible for the review has completed several workshops and is currently consolidating recommendations into a draft proposal. Members discussed: * Public reporting and accountability mechanisms for committee rewards. * Alignment between participation requirements and eligibility for rewards. * The relationship between committee activity, attendance expectations, and reward payments. * Long-term improvements to reward structures and governance participation incentives. #### Decision A motion was raised to amend the current Committee Rewards Policy by extending committee reward payments until 31 December 2026 while the broader policy review continues. Following discussion, the motion was approved with: * 7 votes in favour * 2 abstentions The policy will be updated accordingly. *** ### 5. Budget Process & Treasury Funding Discussion Several participants discussed the current state of the budget process and Intersect’s funding outlook. Topics included: * Current Hydra voting participation and proposal performance. * Potential implications of the Net Change Limit on Treasury Withdrawal submissions. * Ensuring proposals approved through the budget process can proceed to on-chain consideration. * Intersect’s operational runway and funding outlook should future treasury funding not be approved. * Ongoing efforts to reduce operational costs and improve financial sustainability. It was noted that final funding outcomes will become clearer following completion of the current governance and voting processes. *** ### 6. Closing Updates Due to time constraints, updates relating to bylaw voting preparations and upcoming Q2 planning events were deferred for distribution through ISC communication channels following the meeting. *** ### Actions & Next Steps * Launch the Code of Conduct Working Group. * Update the Committee Rewards Policy following the approved amendment. * Continue development of the revised Committee Rewards policy. * Share bylaw voting and Q2 planning updates through ISC communication channels. --- # 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://committees.docs.intersectmbo.org/intersect-steering-committee/committee-meeting-notes/2026-meeting-notes/june-8-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.