# January 19 2026
## Attendees:
| Name | Attendance | Role | Voting Seat (Y/N) |
| ---------------------------------------------------- | ---------- | ------------------------------- | ----------------- |
| [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N |
| Jack Briggs | No | Interim 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 | No | 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 |
| Christian Taylor | Yes | Head of OSO | N |
| 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 | Yes | Secretary of CCC | N |
| Terence McCutcheon | Yes | Secretary of OSC & GMC | N |
| Lara Bonasorte | Yes | Secretary of GMC | N |
### Additional Attendees:
Kyle Solomon - Vice Chair of Product Committee
Thiago Nunes - Observer
Wes Perkinson - Observer
## Agenda:
* Update from Committees
* Open Action & Work in Progress
* 2 year committee term proposal
* AOB & Meeting Close
## Discussion/Actions
### 1. Welcome & Introductions
The meeting opened with attendance confirmation and introductions. The Open Source Committee provided context regarding recent internal changes: due to job transitions, the committee is now operating with six members, and Georg has been confirmed as Chair with Udai Solanki serving as Vice-Chair and acting representative due to scheduling conflicts. Udai introduced himself and shared background on his technical work within the ecosystem.
### 2. Committee Updates
Technical Steering Committee (TSC)\
TSC will join the Product Committee meeting to provide feedback on KPIs, noting this collaboration is intended to be ongoing to support a 2026 roadmap.\
Hard fork work is progressing, with the candidate now expected on node 10.7 (instead of 10.6) due to needed features. Development is on track, though no formal dates have been announced. TSC also:
* finalized work for the Chain Incident Working Group, but publication of the factual report is delayed pending Board approval; members expressed concern over delays
* progressed a Plutus memory limit parameter update, with favorable community feedback and plans for future increases
* highlighted upcoming governance actions that will require SPO voting, requesting stronger communication to SPOs
* noted positive benchmarking results for LSM and coordination with Intersect staff on rollout sequencing
Civics Committee\
The committee’s primary update was the Vice-Chair election currently in progress via the Member Portal, with voting closing Thursday. The committee referenced prior misunderstandings and clarified procedures using notes from last June’s election, reinforcing the need for an MBO-wide Chair/Vice-Chair election policy.\
Working groups (Constitutional Amendments & Governance Education) met recently. A concern was raised that Civics updates did not appear in the weekly Dev Report; Intersect Comms clarified this was due to new cutoff timing and shared how updates will be handled going forward.
Growth & Marketing Committee (GMC)\
GMC is finalizing selection for a new Vice-Chair, with only one member expressing interest so far. KPI review is ongoing, and the committee hosted ServicePlan last week to present on marketing infrastructure. Another agency (Scribe3) may present next week. The committee emphasized that its scope is strategic and planning-focused rather than execution-focused.
Product Committee\
The 2030 Strategy info action is closing today, with participation over 60% and feedback that the current version is considered a positive milestone. Committee members noted that KPIs require substantial further development and alignment work, and activity will now shift toward KPI refinement and preparation for future info actions.
Budget Committee\
The committee is advancing work on a budget feedback loop PRD to capture proposal feedback with provenance and integrate product KPIs and fields directly into the Treasury Budget Template. The NCL info action is now \~40% and DReps are encouraged to vote early given additional actions expected.\
TSC raised the need for structured expert evaluation during future funding rounds; the Budget Committee confirmed this aligns with long-term tooling plans and suggested a follow-up working session with TSC once internal alignment is complete.
### 3. Open Actions & Work in Progress
ISC Secretary provided updates on ongoing work:
* Introduction of a monthly ISC + Board meeting to enable two-way discussion and structured feedback; chairs were encouraged to submit agenda items in advance.
* Work continues on a long-term ISC agenda and work plan; an initial governance planning board (Miro) will be shared next week for feedback.
* 2026 committee goals are being collected; each committee will later present goals during ISC calls (two committees per session) with brief discussion time.
A broader reflection was raised regarding committee workload and mandate clarity. Some members expressed that committees are being overloaded with execution work rather than providing expert guidance and recommendations. Intersect secretaries confirmed this is being reviewed and that secretariat roles will shift toward coordination and support rather than offloading execution onto committees.
### 4. Two-Year Committee Term Proposal
The working group presented a proposal to extend committee terms from 12 to 24 months, based on feedback regarding voter fatigue, election overlap (Board + Committees in October), and continuity. Proposed changes would:
* align committee elections to April annually
* align board elections to October
* reduce operational overhead for committees and staff
* provide more time for members to deliver on multi-quarter goals
Transitional steps were discussed, including potentially extending October 2025 elected members to serve until April 2027 (18 months), with opt-outs and interim elections possible if committees lose capacity.
#### Discussion
Members raised several points:
* Some questioned whether two-year terms are premature given committee maturity, engagement variability, and onboarding challenges.
* Concerns were raised about reduced opportunities for new members, reduced voting opportunities, and potential “power consolidation.”
* Proponents argued continuity is necessary for coherent governance progress and that staggered terms prevent full committee turnover.
* Members also debated whether staggering is needed and how participation/voting rhythm affects member engagement.
Due to time constraints, the ISC agreed to continue discussion next week, rather than call a vote immediately. Supporting documents will be shared for review and commenting.
***
### 5. Next Steps / Actions
* The Chair/Vice-Chair election policy is in final drafting and expected for ISC approval next week.
* An update on Critical Integrations Budget involvement is expected once the Executive Team returns.
The ISC will revisit the two-year term proposal as a main agenda item next week.
---
# 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/january-19-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.