> 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/28th-october-2026.md).

# 28th October 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/13APO7pRL8Wa2ZXfZtkcs874hVAu8UVRL/view?usp=sharing).

## Participants

| Samuel Leathers         | Chair                    | Yes |
| ----------------------- | ------------------------ | --- |
| Alexa C. (Thyme Studio) | Vice-Chair / Voting Seat | Yes |
| Lorenzo Bruno           | Secretary                | Yes |
| Alexandre Maaza         | Voting Seat              | No  |
| Juan Sierra             | Voting Seat              | Yes |
| Yoram Ben-Zvi           | Voting Seat              | Yes |
| James Meidinger         | Voting Seat              | Yes |
| Christian Schmitz       | Voting Seat              | No  |
| Giorgio Zinetti         | Voting Seat              | No  |
| Samir Idris             | Voting Seat              | Yes |
| Jess Fields             | SME                      | Yes |
| Thiago Nunes            | SME                      | Yes |

## Agenda

1. **Review actions and updates**
   * Review latest developments regarding the UNDP contract
2. **Review and discuss the status of milestone PRs submitted by proposers**
   * Address Alexandre Maaza's request for support with the WADA milestone review
3. **Discuss the process for defining 2027 objectives for Pillar 1**
   * Prepare an initial draft of objectives using existing CIPs and product research findings
4. **Review TSC KPI Pull Request**
   * Review outstanding feedback from Leandros
5. **Confirm suitability of the regular committee meeting time**

## Updates

* **Review actions and updates**
  * **Review latest developments regarding the UNDP contract**
    * The Secretary reported that UNDP remained unable to complete contracting due to outstanding wallet and KYB requirements, and the Committee discussed allowing work to begin at the proposer's risk, subject to confirmation from Intersect's legal and procurement teams.
* **Review and discuss the status of milestone PRs submitted by proposers**
  * The Committee reviewed outstanding milestone submissions, confirmed that Token Infrastructure and Elk Milestone 1 had received the required approvals to progress towards payment, and discussed remaining reviews required for other projects.
  * **Address Alexandre Maaza's request for support with the WADA milestone review**
    * The Committee agreed that James Meidinger would take over the WADA review from Alexandre Maaza due to capacity constraints, while Juan Sierra offered to support the outstanding Nextream review.
* **Discuss the process for defining 2027 objectives for Pillar 1**
  * **Prepare an initial draft of objectives using existing CIPs and product research findings**
    * The Chair confirmed that an initial draft of Pillar 1 infrastructure objectives would be developed using existing CIPs and relevant research findings, with the discussion continuing in the next session and a target to progress the work by the end of November.
* **Review TSC KPI Pull Request**
  * **Review outstanding feedback from Leandros**
    * The Committee confirmed that feedback had been submitted on the TSC KPI Pull Request and that Leandros had acknowledged the comments, with a detailed response still pending.
* **Confirm suitability of the regular committee meeting time**
  * The Committee discussed the impact of daylight saving time changes on members in different time zones and agreed to revisit the meeting schedule in the following session to confirm its suitability, particularly for members based in the United States.

## 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/28th-october-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.
