> 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/22nd-july-2026.md).

# 22nd July 2026

The session was run in the related [miro board](https://miro.com/app/board/uXjVKro_lxs=/). 

📽️ The meeting recording can be found [here](https://drive.google.com/file/d/12phl3CyP3hpjjVsBozcdV0tHgZGvKhp7/view?usp=sharing).

## Participants

| Name                    | Role                               | Attendance |
| ----------------------- | ---------------------------------- | ---------- |
| Samuel Leathers         | Chair                              | Yes        |
| Lorenzo Bruno           | Secretary                          | No         |
| Alexandre Maaza         | Voting Seat (Vice-Chair Appointee) | No         |
| Juan Sierra             | Voting Seat                        | Yes        |
| Yoram Ben-Zvi           | Voting Seat                        | No         |
| 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                        | No         |

## Agenda

* Discuss CPC support for the Dijkstra scope
* Discuss future hard fork planning
* Review actions and updates
  * bylaws voting
  * Product Research X post shared last week
  * Product Research contracts out for signature (5 out of 7)
    * waiting on Prisma reply
  * GMC sync booked
* Product Research – approve UNDP reply
* Review survey to gather more feedback on KPIs – review Thyme Studio’s presentation and feedback

## Updates

* **Discuss CPC support for the Dijkstra scope**
  * The Chair presented the proposed phased Dijkstra rollout and scope, and the Committee supported publishing the scope to the Product Committee website while awaiting TSC feedback.
* **Discuss future hard fork planning**
  * The Chair reviewed the proposed hard fork planning process, including joint CPC and TSC ownership of scope, community participation through the Hard Fork Working Group, and different funding paths based on engineering effort.
* **Review actions and updates**
  * **Bylaws voting**
    * The Chair reminded eligible Committee members to complete the required KYC process and vote on the bylaws.
  * **Product Research X post shared last week**
    * No discussion for this topic was held.
  * **Product Research contracts out for signature (5 out of 7)**
    * The Committee was informed that five of the seven Product Research contracts had been sent for signature, with the remaining two dependent on outstanding matters concerning UNDP and Prisma.
  * **Waiting on Prisma reply**
    * The Committee was informed that a reply from Prisma remained outstanding before its Product Research contract could progress.
  * **GMC sync booked**
    * No discussion for this topic was held.
* **Product Research**
  * **Approve UNDP reply**
    * The Committee reviewed UNDP’s response regarding the removal of a team member from its proposal and agreed that the change was procedural and could progress.
* **Review survey to gather more feedback on KPIs**
  * **Review Thyme Studio’s presentation and feedback**
    * The Committee reviewed the proposed KPI feedback survey, discussed its structure, length, timing and distribution, and supported progressing it with minor adjustments before sharing it with other committees.

## 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/22nd-july-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.