# June 16, 2025 ISC Meeting
## Agenda
* ISC Actions/Update from last week
* Smart Contract Testing
* Draft Decision Making Framework
* Update from Committees and Business Functions (If Any)
* AOB & Meeting Close
## Attendees:
| Name | Attendance | Role | Voting Seat (Y/N) |
| ---------------------------------------------------- | ---------- | ------------------------------- | ----------------- |
| [Simo Simovic](mailto:simo.simovic@intersectmbo.org) | Yes | Secretary | N |
| Jack Briggs | Yes | Interim Executive Director | Y |
| Nick Cook | No | Director - Operations (Interim) | Y |
| YUTA | Yes | Community Member Seat | Y |
| Phil Lewis | Yes | Community Member Seat | Y |
| Sheldon Hunt | Yes | Community Member Seat | Y |
| Fred Tanaka | Yes | Community Member Seat | Y |
| Pedro Lucas | Yes | OSC Chair | Y |
| Samuel Leathers | Yes | Product Chair | Y |
| Darlington Welsh | Yes | MCC Chair | Y |
| Kristijan Kowalsky | Yes | CBC Chair | Y |
| Kevin Hammond | No | TSC Chair | Y |
| Wes Parkison | No | GMC Chair | Y |
| Nicolas Cerny | Yes | Interim CCC Chair | Y |
| Christian Taylor | Yes | Head of OSO | N |
| Lorenzo Bruno | Yes | Head of Product | N |
| Matt Davis | Yes | Head of Tech Operation | N |
| Duncan Soutar | Yes | Secretary of TSC | N |
| Lloyd Duhon | No | Secretary of Budget Committee | N |
| Larisa Mcfarlane | Yes | Secretary of CCC | N |
| Terence McCutcheon | Yes | Secretary of OSC | N |
Additional Attendees:
Kyle Solomon - Observer
Thiago Nunes - Observer
## Discussion/Action:
### 1. Opening and Introductions
The meeting began with a welcome to all participants, including the newly elected chair of the Budget Committee. The ISC secretary outlined the agenda, which included a review of current action items, updates on budget implementation and treasury withdrawals, presentation of the draft decision-making framework, and committee-related updates.
### 2. Review of Action Items and Planning
Several ongoing items were reviewed.
* The consultant transition plan has been finalized and will be presented to the board later this month.
* The ISC confirmed its participation as observers in the upcoming board meeting scheduled for June 26, with preparations underway.
* Upcoming Intersect AMA is scheduled for June 27. The process and agenda are finalized, marking the first in a recurring series aimed at increasing transparency and engagement with the broader community.
* The leadership team is working on a contingency plan in case the 2025 budget is not approved. While the budget vote passed successfully, a formal fallback process is being documented, and will be brought to the ISC and board for review in early July.
### 3. Smart Contract Testing and TW Budget Execution
Following the successful passage of the 2025 Intersect budget through on-chain governance, attention has turned to execution. Smart contract development and testing—conducted by Sundae Labs—is proceeding well. Internal and mainnet testing is underway with the goal of submitting all 39 individual treasury withdrawal actions at the start of the next epoch.
The team clarified that while some funded vendors are ready to begin work, contracts must be finalized and signed before formal onboarding. Roughly 70 to 80 contracts are expected to be issued in this initial cycle.
The ISC discussed the idea of issuing a prioritization guide to help DReps and ICC identify which proposals are particularly time-sensitive (e.g. Intersect operations, Catalyst administration, and Cardano Summit logistics). While this would not affect the order of submission, it could provide helpful context during voting and oversight.
### 4. Draft Decision-Making Framework
Intersect staff presented a draft of the decision-making framework intended to clarify how decisions move through the governance structure—from working groups to committees, through the ISC, and where appropriate, to the board or wider community.
The framework categorizes different types of decisions: internal operational matters, governance actions, and externally-facing proposals. It aims to describe existing processes, not introduce new bureaucracy. Emphasis was placed on balancing standardization with committee autonomy, and avoiding bottlenecks.
The ISC agreed the framework should be tested using real-world examples and refined through an upcoming workshop. There was consensus that this process can support long-term clarity and institutional memory without slowing down day-to-day decision-making.
### 5. Additional Committee Updates and Reflections
Several members raised the need to ensure early execution of critical proposals, particularly those that enable broader ecosystem activity or provide alternative funding pathways (e.g., Catalyst and Builder DAO). Delays in these areas could have downstream impacts. The ISC acknowledged this and reiterated the importance of agility and preparedness in future funding cycles.
It was noted that the Budget Committee is planning a retrospective to review this cycle’s process and gather feedback from all stakeholders. This may be conducted in part during community events such as Rare Evo.
### Action Items & Next Steps
* Submit 39 individual treasury withdrawals in one coordinated batch.
* Coordinate ISC observer participation in the June Intersect Board meeting.
* Refine and test the decision-making framework in a practical workshop setting.
---
# 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/2025-meeting-notes/june-16-2025-isc-meeting.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.