> 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-product-committee/committee-meeting-notes/2026/21st-october-2026.md).

# 21st October 2026

The session was run in the related [miro board](https://miro.com/app/board/uXjVKro_lxs=/).&#x20;

📽️ The meeting recording can be found [here](https://drive.google.com/file/d/1wXZUE_F8xXTPrX-wMbSurFbi1RTcRmEt/view?usp=sharing).

## Participants

| Samuel Leathers         | Chair                    | Yes |
| ----------------------- | ------------------------ | --- |
| Alexa C. (Thyme Studio) | Vice-Chair / Voting Seat | Yes |
| Lorenzo Bruno           | Secretary                | Yes |
| Alexandre Maaza         | Voting Seat              | Yes |
| Juan Sierra             | Voting Seat              | Yes |
| Yoram Ben-Zvi           | Voting Seat              | Yes |
| James Meidinger         | Voting Seat              | Yes |
| Christian Schmitz       | Voting Seat              | No  |
| Giorgio Zinetti         | Voting Seat              | No  |
| Samir Idris             | Voting Seat              | Yes |

**Additional attendees:** Kevin Hammond, Simo Simovic, Abdulbasit Adigun Abdulrahman, Benjamin Ben Zvi, Ken-Erik Ølmheim and Musa Ridwan Itopa.

## Agenda

1. **Review actions and updates**
2. **Review and discuss the status of milestone PRs submitted by proposers**
3. **Review TSC KPI Pull Request**
4. **Discuss the process for defining 2027 objectives for Pillar 1**
   * Review existing CIPs to identify potential infrastructure objectives
   * Engage community stakeholders to identify infrastructure needs
   * Incorporate findings from ongoing product research
   * Explore translating identified needs into CPSs or CIPs
   * Continue the discussion in the next session

## Updates

* **Review actions and updates**
  * The Secretary confirmed that the UNDP contract remained unsigned while the organisation finalised its wallet arrangements, and the Committee supported setting 2 November as a deadline before reconsidering alternative proposers.
* **Review and discuss the status of milestone PRs submitted by proposers**
  * The Committee reviewed outstanding milestone submissions and identified missing reviews across several projects, emphasising the need to prioritise Milestone 1 approvals to enable payments to proposers.
  * The Chair clarified the GitHub review process, supported the assignment of reviewers directly to PRs and encouraged members to complete their reviews by the end of the week.
* **Review TSC KPI Pull Request**
  * The Chair presented feedback on the TSC KPI Pull Request, identifying discrepancies in Plutus growth projections and assumptions about the protocol revenue required to replace treasury reserve distributions.
  * The Committee discussed the gap between Cardano's sustainability targets and current adoption, highlighting the importance of a coordinated strategy, clearer budget priorities and actionable plans to achieve the 2030 objectives.
  * The TSC representative agreed to share the technical feedback with the relevant contributors, while the Committee was encouraged to submit further comments directly through the PR.
* **Discuss the process for defining 2027 objectives for Pillar 1**
  * **Review existing CIPs to identify potential infrastructure objectives**
    * The Committee discussed using existing CIPs and proposed protocol improvements as a starting point to identify infrastructure development priorities aligned with Pillar 1 of the Cardano 2030 Strategy.
  * **Engage community stakeholders to identify infrastructure needs**
    * The Committee discussed consulting ecosystem developers, infrastructure providers and other relevant stakeholders to identify technical limitations and capabilities needed to support Cardano adoption.
  * **Incorporate findings from ongoing product research**
    * The Chair suggested leveraging findings from the ongoing product research initiatives to identify infrastructure limitations and development opportunities relevant to future objectives.
  * **Explore translating identified needs into CPSs or CIPs**
    * The Committee discussed how identified needs could inform new Cardano Problem Statements or be developed into technical improvement proposals with support from engineering teams.
  * **Continue the discussion in the next session**
    * The Secretary proposed returning to the topic in the following session to further develop the process for defining 2027 infrastructure objectives, while maintaining milestone reviews as the immediate priority.

## Outcomes & Recommendations

N/A

## Decisions Recorded

N/A


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://committees.docs.intersectmbo.org/intersect-product-committee/committee-meeting-notes/2026/21st-october-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
