> 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/2nd-september-2026.md).

# 2nd September 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/1bNLk_hj2OP14v9eOyP_FY7GJDMlfI5yg/view?usp=sharing).

## Participants

| Name                    | Role        | Attendance |
| ----------------------- | ----------- | ---------- |
| Samuel Leathers         | Chair       | Yes        |
| Lorenzo Bruno           | Secretary   | No         |
| Alexandre Maaza         | Voting Seat | No         |
| Juan Sierra             | Voting Seat | Yes        |
| Yoram Ben-Zvi           | Voting Seat | Yes        |
| Alexa C. (Thyme Studio) | Vice-Chair  | 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
  * confirm milestone submission and review process communicated to proposers
  * confirm research funds unlocked
  * update on UNDP contract
  * confirm committee focus weeks and upcoming planning
* Review CPC KPI survey
  * review status and feedback
* Agree on committee focus weeks
* Review any milestone pull requests raised by proposers

## Updates

* **Review actions and updates**
  * **Confirm milestone submission and review process communicated to proposers**
    * The Committee confirmed that proposers had been provided with the milestone submission process and that three milestone pull requests had been received for Committee review.
  * **Confirm research funds unlocked**
    * The Chair confirmed that the CR to unlock funds for the research proposals had been signed, enabling payments to proceed as milestones are completed.
  * **Update on UNDP contract**
    * The Chair reported that the UNDP contract remained pending on the other party's side and was expected to progress within the coming weeks.
  * **Confirm committee focus weeks and upcoming planning**
    * The Chair confirmed plans to hold a meeting during the second-to-last week of September and take the final week of September and first week of October as committee focus weeks.
* **Review CPC KPI survey**
  * **Review status and feedback**
    * The Committee reviewed the KPI survey status, with four of seven committees having submitted responses and six expected by 9 September, while concerns were raised about whether the Steering Committee response represented an agreed committee position.
* **Agree on committee focus weeks**
  * The Committee confirmed its September and October schedule and noted that upcoming planning would cover Q3 achievements and Q4 priorities ahead of the quarterly events.
* **Review any milestone pull requests raised by proposers**
  * The Committee reviewed the milestone-review arrangements, confirmed that reviewers should comment directly on assigned GitHub pull requests, and agreed that reviews should consider both compliance with agreed requirements and the value delivered to the Cardano community.

## 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/2nd-september-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.
