> 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/23rd-september-2026.md).

# 23rd 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/1xJPnp89d5ssKygOYGAM6lUMcuO-p3xxu/view?usp=sharing).

## Participants

| Samuel Leathers         | Chair       | Yes |
| ----------------------- | ----------- | --- |
| Alexandre Maaza         | Voting Seat | No  |
| Lorenzo Bruno           | Secretary   | No  |
| Juan Sierra             | Voting Seat | No  |
| Yoram Ben-Zvi           | Voting Seat | No  |
| 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 | No  |

**Additional attendees:** Nana Safo and Terence McCutcheon.

## Agenda

1. **Review actions and updates**
   * Review outstanding UNDP wallet address and contract status
2. **Review milestone PRs submitted by proposers**
3. **Review TSC KPI Pull Request**
4. **Confirm quarterly reporting and upcoming meeting schedule**

## Updates

* **Review actions and updates**
  * **Review outstanding UNDP wallet address and contract status**
    * The Committee confirmed that the UNDP contract remained pending receipt of the required wallet address, with no response received, and discussed following up through existing contacts.
* **Review milestone PRs submitted by proposers**
  * The Chair reviewed the status of submitted research milestones and clarified the GitHub review process, including the requirement for reviewers to formally approve or request changes rather than only leave comments.
  * The Committee identified outstanding reviews across several proposals, including Nextrium, Token Infrastructure, Elk, WADA and Prisma, and discussed following up with assigned reviewers.
  * The Committee also discussed using AI to support milestone assessments and proposed creating a short instructional video to help members complete GitHub reviews correctly.
* **Review TSC KPI Pull Request**
  * The Chair confirmed that the review of the TSC KPI Pull Request would likely resume after Token2049 due to existing commitments and availability.
* **Confirm quarterly reporting and upcoming meeting schedule**
  * The Committee confirmed that the Chair and Alexa C. would present the quarterly progress report at the upcoming Intersect Steering Committee session, using the presentation prepared by the Secretary.
  * The Committee confirmed that the next two regular sessions would be cancelled to accommodate quarterly activities and Token2049, with members continuing milestone reviews asynchronously before resuming meetings on 14 October.

###

## 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/23rd-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.
