> 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/4th-november-2026.md).

# 4th November 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/1QspDfM_K6ST6rdB8Z4tEqNPvUOg6T6IN/view?usp=sharing).

## Participants

| Name                    | Role                     | Attendance |
| ----------------------- | ------------------------ | ---------- |
| Samuel Leathers         | Chair                    | No         |
| Alexa C. (Thyme Studio) | Vice-Chair / Voting Seat | Yes        |
| Lorenzo Bruno           | Secretary                | Yes        |
| Alexandre Maaza         | Voting Seat              | Yes        |
| 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              | No         |

**Additional attendees:** Abdulbasit Adigun Abdulrahman, Burcu Mavis (UNDP), Marco Moshi and Nana Safo.

## Agenda

1. **Review actions and updates**
   * Share updates on the Intersect committee review process
2. **Review and discuss the status of milestone PRs submitted by proposers**
3. **Review UNDP research project and contracting progress**
4. **Discuss GMC activities and coordination with CPC**
5. **Discuss the process for defining 2027 objectives for Pillar 1**
   * Prepare initial objectives for Infrastructure & Research Excellence
6. **Discuss additional topic proposed by Jess Fields**
7. **Review suitability of the regular committee meeting time**

## Updates

* **Review actions and updates**
  * **Share updates on the Intersect committee review process**
    * The Secretary provided an update on the ongoing committee effectiveness review, including findings from surveys, focus groups and interviews, and discussed the proposed committee restructuring being considered by the Intersect Steering Committee.
* **Review and discuss the status of milestone PRs submitted by proposers**
  * The Committee reviewed outstanding milestone submissions and payment readiness, confirming progress on approved milestones for AISA, Elk and Token Infrastructure while identifying remaining reviews for Nextream, WADA and Prisma.
  * The Committee discussed feedback on WADA's milestone submission, clarifying that the signed contract's acceptance criteria take precedence over the original proposal and that the proposer remains responsible for its internal allocation of funds.
* **Review UNDP research project and contracting progress**
  * The Committee received a presentation from UNDP outlining its blockchain initiatives, Government Blockchain Academy and planned research into government adoption opportunities, including the identification of use cases that could support Cardano's adoption in emerging markets.
  * Alexandre Maaza provided an update on the proposed contracting arrangement involving the Cardano Foundation, Intersect and UNDP to address outstanding procurement and payment requirements, with the relevant teams expected to coordinate the next steps.
* **Discuss GMC activities and coordination with CPC**
  * The Committee received an update from GMC on its ecosystem capability mapping and industry vertical initiatives, including ongoing work to consolidate research findings and identify opportunities for collaboration across committees.
  * The Committee discussed the importance of translating research and strategic frameworks into practical adoption plans, measurable KPIs and clear ownership of delivery.
* **Discuss the process for defining 2027 objectives for Pillar 1**
  * **Prepare initial objectives for Infrastructure & Research Excellence**
    * The Secretary confirmed that an initial set of three to five objectives would be developed for the relevant areas of Pillar 1, with the discussion deferred to the next session pending further input from the Chair.
* **Discuss additional topic proposed by Jess Fields**
  * No discussion for this topic was held, as Jess Fields was not present to introduce it.
* **Review suitability of the regular committee meeting time**
  * The Committee discussed the impact of time zone differences and the overlap with TSC meetings, and the Secretary agreed to circulate a proposal through Slack to explore moving the regular session to a later time.

## 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/4th-november-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.
