> 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-2.md).

# 19th August 2025

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/14V48mh_sjS6Y2LUZFPxP8d_0rT2Kce_Q/view?usp=sharing).

## Participants

| Name                    | Role                               | Attendance |
| ----------------------- | ---------------------------------- | ---------- |
| Samuel Leathers         | Chair                              | Yes        |
| Lorenzo Bruno           | Secretary                          | Yes        |
| Alexandre Maaza         | Voting Seat (Vice-Chair Appointee) | No         |
| 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&#x20;
  * follow up on the outstanding UNDP response
* Review Product Research milestones for Wada and TKNFRA
* Review the KPI survey as the Product Committee
* Discuss 2027 deliverables

## Updates

* **Review actions and updates**
  * **Follow up on the outstanding UNDP response**
    * The Secretary reported that the UNDP proposal remained pending because responses to outstanding questions had not been received, with a further follow-up planned before considering allocation to the next proposal in line.
* **Review Product Research milestones for Wada and TKNFRA**
  * The Committee received milestone presentations covering research into Cardano’s commercial positioning for AI and adoption opportunities in Africa, and discussed stakeholder outreach, research validation, milestone review and publication of milestone reports.
* **Review the KPI survey as the Product Committee**
  * The Committee reviewed and agreed its survey responses, including adoption and utility as the most relevant strategic pillar, concerns with existing KPI measurement, proposed additional KPIs, and the need for consistent ownership and tracking of KPI data.
* **Discuss 2027 deliverables**
  * No discussion for this topic was held. The Secretary noted that the item could be covered at the following meeting due to the limited time remaining.

## 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-2.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.
