> 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-17-2026.md).

# August 17 2026

## Attendees:&#x20;

| 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                 |
| 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                                        | Yes        | 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                                     | Yes        | Head of Ecosystem & Community | Y                 |
| Nick Clarke                                          | No         | Head of Cardano Technology    | N                 |
| Bosko Majdanac                                       | Yes        | Secretary of TSC              | N                 |
| Abhik Nag                                            | Yes        | Secretary of MCC              | N                 |
| Terence McCutcheon                                   | Yes        | Secretary of OSC              | N                 |
| Lara Bonasorte                                       | Yes        | Secretary of GMC              | N                 |
| Thomas Lindseth                                      | Yes        | Secretary of CCC              | N                 |

### Additional Attendees:

Geoff Watson - Director of Technology (IO)

Ken-Erik Ølmheim - Vice Chair of Civics

Thyme Studio - Vice Chair of Product

Selin Rhayem - Observer

## Agenda:&#x20;

* Committee Update&#x20;
* Leios and Dijakstra Update
* Constitution Amendment Process Update
* Board Election Timeline
* AOB

## Discussion/Actions

### 1. Committee Updates

* Civics Committee: The committee reviewed the second deliverable from the Constitutional Amendments Working Group, covering progress including the launch of the alpha version of the Constitution Amendment Process (CAP), with a vote planned for the week. Members also reviewed the live Constitutional Committee update governance action and raised concern about low SPO participation. The committee plans to strengthen outreach, including coordination with ecosystem partners and development of a broader social media engagement plan.
* Technical Steering Committee: The committee is reviewing IOG's plans for the Dijkstra hard fork and providing input on Leios. Attention is also focused on increasing SPO participation in the live parameter update governance action and developing the TSC's budget spending profile for the coming year.
* Growth & Marketing Committee: Work continued with the Product Committee on the vertical qualification framework and agriculture research structure, including research into competitive market frameworks and DeFi. The committee is also considering how it can support ecosystem events and Cardano Foundation initiatives, coordinating work on quantum resistance, and converting the "From Capability to Adoption" paper into more accessible communications materials.

### 2. Leios and Dijkstra Update

IOG presented an update on the delivery plan for Leios and the Dijkstra hard fork. The current target remains to deliver Leios during 2026, with December 5 identified as the target hard fork date. The timeline was acknowledged as challenging and dependent on completing development, testing, Intersect technical and governance checks, and securing sufficient SPO participation.

SPO adoption was identified as one of the key dependencies. Testing is being conducted incrementally to understand the transaction throughput that can be supported without creating unreasonable infrastructure costs for SPOs. The rollout is expected to be gradual, balancing network performance, adoption, demand, and infrastructure requirements.

The group also discussed the relationship between the Dijkstra hard fork and required constitutional amendments. Further coordination is needed to determine the appropriate sequencing of the hard fork, new parameters, constitutional guardrails, and the rollout of Leios. A dedicated discussion will be arranged between relevant technical and Constitutional Committee representatives to work through the approach.

### 3. Constitution Amendment Process Update

The Constitution Amendment Process remains a standing ISC agenda item and will continue to be tracked through the end of the year. No new proposals had been submitted since the previous meeting, although additional community comments had been received on existing proposals.

Discussion focused particularly on proposals related to evolving the Net Change Limit into a more strategic spending framework, treasury withdrawal requirements, and milestone-based treasury disbursement. Members were encouraged to review and comment on proposals relevant to their areas of expertise.

The group also discussed how much constitutional change should be attempted alongside Dijkstra. There was support for prioritizing only the constitutional changes necessary for the upgrade rather than attempting to include all outstanding proposals in a single amendment. Broader constitutional improvements could then progress through a subsequent amendment process.

### 4. Board Election Timeline

The timeline for the September Board election was presented. Communications will run from August 18, with applications opening on August 31 and closing on September 11. Member voting will run from September 14–25, followed by an independent third-party audit. Final results are planned for September 28, allowing newly elected Board members to begin onboarding during October. Two elected Board seats are available in this election.

The KYC process has been updated following feedback from the recent Bylaws vote, including removal of the proof-of-address requirement. A campaign will encourage eligible members to complete KYC before voting begins on September 14. Members who completed the required KYC for the Bylaws vote will not need to repeat the process for the Board election.

The current Board composition was also clarified. Four seats are held by elected members and three by appointed/sustaining members. EMURGO's departure has created a vacancy among the appointed seats, which remains under Board consideration.

### 5. Cardano 2030 Goals and KPI Discussion

Committees were reminded to provide feedback on the Cardano 2030 KPI survey. The Budget Committee indicated that it intends to provide its feedback through a dedicated document rather than the survey, allowing it to address broader questions around ownership, accountability, tracking, and annual ecosystem goals.

This led to a broader discussion about the purpose of the KPI exercise and the need for clearer strategic direction. Members discussed the distinction between defining ecosystem goals and identifying metrics to measure progress, as well as the lack of clear ownership and accountability for Cardano 2030 KPIs. There was particular interest in establishing more tangible ecosystem goals and strategic priorities for 2027 that could help guide future treasury funding decisions.

The group agreed that the subject requires further discussion, with a dedicated follow-up to clarify whether the focus should be on revisiting Cardano's strategic goals, the associated KPIs, or both.

### 6. Actions & Next Steps

* Arrange a dedicated discussion between relevant technical and Constitutional Committee representatives on the Dijkstra/Leios rollout and constitutional amendment sequencing.
* Continue providing Leios/Dijkstra progress updates to the ISC, potentially on a bi-weekly basis.
* Add a dedicated follow-up discussion on Cardano 2030 goals, KPI ownership, accountability, and 2027 strategic priorities to an upcoming ISC agenda.


---

# 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-17-2026.md?ask=<question>&goal=<endgoal>
```

`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.
