# March 2 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 |
| Nick Cook | No | Director - Operations (Interim) | Y |
| Sheldon Hunt | Yes | Community Member Seat | Y |
| Fred Tanaka | Yes | Community Member Seat | Y |
| Kristijan Kowalsky | Yes | Community Member Seat | Y |
| Jose Miguel de Gamboa | Yes | Community Member Seat | Y |
| Georg Link | No | OSC Chair | Y |
| Samuel Leathers | Yes | Product Chair | Y |
| Maureen Wepngogn | Yes | MCC Chair | Y |
| Megan Hess | Yes | CBC Chair | Y |
| Kevin Hammond | Yes | TSC Chair | Y |
| Tim Harrison | No | GMC Chair | Y |
| Nicolas Cerny | Yes | CCC Chair | Y |
| Lorenzo Bruno | Yes | Secretary of CPC | N |
| Bosko Majdanac | Yes | Secretary of TSC | N |
| Abhik Nag | Yes | Secretary of MCC | N |
| Lloyd Duhon | Yes | Secretary of Budget Committee | N |
| Larisa Mcfarlane | No | Secretary of CCC | N |
| Terence McCutcheon | Yes | Secretary of OSC & GMC | N |
| Lara Bonasorte | Yes | Secretary of GMC | N |
### Additional Attendees:
Adam Rusch - Member of the Intersect Board
Mercy Fordwoo - Member of the Intersect Board
Nikhil Joshi - Member of the Intersect Board
Ken-Erik Ølmheim - Vice Chair of Civics
Kyle Solomon - Vice Chair of Product
Mike Hornan - Observer
Thiago Nunes - Observer
Wes Parkinson - Observer
## Agenda:
* Update from Committees
* Committee Chair & Vice-Chair Election Policy
* Committee role and responsibility
* Draft committee budget
* AOB & Meeting Close
## Discussion/Actions
### 1. Opening & Agenda
The meeting opened with attendance confirmation and review of the agenda. Initial quorum was uncertain, but additional members joined during the meeting and quorum was confirmed before voting activities. The agenda included committee updates, review and approval of the Committee Chair & Vice-Chair Election Policy, discussion of committee roles and responsibilities guidance, and an initial review of draft committee budget work packages.
### 2. Committee Updates
* Technical Steering Committee (TSC) reported ongoing work across several areas, including progress on simulations related to the linear-leases update and continued collaboration with the Product Committee on Vision 2030 KPI refinement. The hard fork workstream is advancing, with the protocol version 11 hard fork confirmed to be named “Van Rossum.” The hard fork working group has increased its meeting frequency as preparations intensify. A temporary issue occurred on testnet related to the Plutus cost model update but was identified and corrected. TSC also reviewed potential updates to Constitution v2.4 and plans to provide feedback to the Civics Committee. In preparation for upcoming elections, TSC discussed the number of committee seats and may consider co-opting an additional member depending on election results.
* Growth & Marketing Committee (GMC) shared updates on work toward an enterprise onboarding framework being developed alongside an enterprise onboarding working group. The committee is exploring approaches where enterprises propose marketing strategies directly to the community rather than relying on a centrally proposed strategy. A discussion also surfaced regarding the current status of the unified Cardano event strategy and ecosystem event participation, with differing understandings between participants. It was agreed that this topic would be clarified through follow-up discussions outside the meeting.
* Product Committee reported progress in developing its draft budget work packages and continuing work on refining Vision 2030 KPIs. The product research grant round closed the previous week, and the review phase for submitted proposals is beginning.
* Open Source Committee (OSC) reported progress on preparing its budget proposal and confirmed alignment among committee members on the draft direction. The committee expressed a preference for a longer-term budget horizon if feasible, while acknowledging that the final duration will depend on the broader Intersect budget framework.
### 3. Committee Roles & Responsibilities (Guidance Document)
The Governance Working Group presented an early version of a document outlining high-level roles and responsibilities for committee members, chairs, and secretaries. The document is intended primarily as onboarding guidance for newly elected committee members and to provide a consolidated reference across committees.
The guidance clarifies the advisory role of committee members, participation expectations, and the relationship between committees, working groups, Intersect staff, and vendors when executing work. Participants generally supported the direction of the document as an initial version, with further refinements planned in later iterations. The Governance Working Group will also revisit the committee dismissal policy in future sessions to ensure alignment with these responsibilities.
### 4. Committee Chair & Vice-Chair Election Policy
The Committee Chair & Vice-Chair Election Policy was formally presented for approval. The policy aims to standardize how committees elect leadership positions following committee elections, replacing previous variations in practice across committees.
During discussion, members raised clarifications regarding the process for leadership transitions and responsibilities for initiating elections when a chair steps down. An amendment was proposed specifying that the committee secretary is responsible for initiating an election within two official committee meetings when a vacancy occurs. After incorporating this clarification, the motion to approve the policy was formally proposed and seconded.
The policy was approved by vote, with the majority voting in favor and one abstention.
### 5. Committee Budget Work Packages
Committees began presenting draft work packages for their 2026 budget planning. These proposals will help align committee initiatives with the broader Intersect budget proposal and ensure there are no overlaps or gaps between committee activities and Intersect operational priorities.
The Budget Committee presented four proposed priority areas:
* Facilitation of the 2027 budget process, including retrospective analysis and process improvements
* Budget tooling upgrades, including smart contract improvements
* Support for treasury withdrawal financial audit preparation and review
* A proposed Treasury Transparency Initiative Program (TTIP) to provide tools and educational resources enabling the community to better understand treasury activity and on-chain financial data
The Product Committee briefly shared early concepts for several work packages, including ongoing Vision 2030 strategy work, development of annual ecosystem goals aligned with strategic pillars, KPI tracking dashboards, and research into emerging ecosystem opportunities. These proposals remain in an early draft stage and will be refined in upcoming meetings.
Members noted the importance of also mapping Intersect’s own operational work packages to the same planning board to provide a complete view of ecosystem and organizational activities.
### 6. Closing
The meeting concluded with agreement that committees will continue refining their draft budget proposals and provide feedback through the shared planning board. Further alignment with the executive team and the Board will occur as part of the broader budget preparation process.
***
### Actions & Next Steps
No new formal actions were assigned during this meeting.
---
# Agent Instructions: 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:
```
GET https://steeringcommittee.docs.intersectmbo.org/committee-meeting-notes/2026-meeting-notes/march-2-2026.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.