> For the complete documentation index, see [llms.txt](https://productcommittee.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://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/24th-june-2026.md).

# 24th June 2026

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

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

## Participants

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

## Agenda

* Review actions and updates
  * Ecosystem Funding Working Group (EFWG)
  * Vice-Chair appointment
* Product research
* Planning
* CBC survey questions
* Review KPI document from TSC
  * Review proposed changes with current status (in Miro)
  * Agree feedback to TSC

## Updates

* **Review actions and updates**
  * **Ecosystem Funding Working Group (EFWG)**
    * The Committee received an update on the Ecosystem Funding Working Group, including the onboarding of a contractor, the development of a funding coordination framework, and opportunities to align the work with the Product Committee’s KPI refinement activities.
  * **Vice-Chair appointment**
    * The Secretary confirmed that Alexandre Maaza had withdrawn from the Vice-Chair role, Alexa C. (Thyme Studio) volunteered to stand for the position, and the Committee agreed to open the opportunity to all members before conducting an asynchronous vote.
* **Product research**
  * The Chair confirmed that proposal reviews had been completed, the final report was being anonymised before publication, and the Committee reviewed the proposed list of projects recommended for funding.
  * The Committee discussed publication of the evaluation report, reviewer anonymity, audit considerations, communications to the community, expected contract structure, and delivery requirements for successful research proposals.
* **Planning**
  * The Secretary reviewed the Committee's Quarter 3 workstreams, including issuing research contracts, monitoring research progress, completing KPI refinement activities, and preparing future planning aligned with the 2030 Vision.
  * The Committee agreed to continue engagement with the Growth & Marketing Committee, request feedback from additional committees through a survey, and consider producing KPI guidance for committees during Quarter 4.
  * The Committee discussed future funding options following the unsuccessful treasury withdrawal proposal and considered using completed research outputs to support future pilot funding proposals.
* **CBC survey questions**
  * The Committee received an update from the Budget Committee that a post-budget process survey would be distributed to participants, and members agreed to support and complete the survey once available.
* **Review KPI document from TSC**
  * **Review proposed changes with current status (in Miro)**
    * The Committee reviewed progress on KPI refinement, discussed alignment of committee planning with the 2030 Vision, and considered improvements to committee-wide KPI adoption and governance.
  * **Agree feedback to TSC**
    * No discussion for this topic was held.

## 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://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/24th-june-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.