> 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/20th-february-2025-4.md).

# 5th August 2025

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/1R12orD6yli420a5AurEEB8B5I0jBHsVv/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                        | Yes        |
| Christian Schmitz       | Voting Seat                        | No         |
| Giorgio Zinetti         | Voting Seat                        | No         |
| Samir Idris             | Voting Seat                        | Yes        |

## Agenda

* Review actions and updates
  * update on Product Research
  * GMC meeting scheduled for next week
* Review Ecosystem Funding Working Group next steps
* Prepare for the GMC meeting

## Updates

* **Review actions and updates**
  * **Update on Product Research**
    * The Secretary reported that five of seven Product Research contracts had been signed and work had started, while outstanding information was still awaited from UNDP and Prisma; the first milestone from one research project had also been completed.
  * **GMC meeting scheduled for next week**
    * The Secretary confirmed that the GMC meeting had been moved to the following week and that the Committee would use the additional time to prepare its agenda.
* **Review Ecosystem Funding Working Group next steps**
  * The Committee received an update on progress with the ecosystem funding architecture project, including its diagnostic, architecture and community handover phases, and discussed how to gather wider Intersect feedback and coordinate the eventual handover.
* **Prepare for the GMC meeting**
  * **KPIs**
    * The Committee agreed that the GMC discussion should cover KPI alignment and noted that the recently released KPI survey could support coordination between the committees.
  * **Product Research**
    * The Committee agreed to discuss the funded Product Research initiatives with GMC to align on research scope, avoid overlap and establish an effective approach for ongoing coordination.

## 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 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://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/20th-february-2025-4.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.