> 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/29th-july-2026.md).

# 29th 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/1GdNgwrNPmrIS2UiIMct9yyHs7s842BD8/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                        | No         |
| Christian Schmitz       | Voting Seat                        | No         |
| Giorgio Zinetti         | Voting Seat                        | No         |
| Samir Idris             | Voting Seat                        | No         |

## Agenda

* Review actions and updates
  * Product Research contracts: 5 out of 7 completed and awaiting signature, with 2 proposers unresponsive
* Approve release of the KPI feedback survey
* Review any updates on the Dijkstra hard fork

## Updates

* **Review actions and updates**
  * **Product Research contracts: 5 out of 7 completed and awaiting signature, with 2 proposers unresponsive**
    * The Committee reviewed the status of the Product Research contracts and discussed an outstanding concern with the proposed milestone structure for releasing funds, which the Secretary was working to address.
* **Approve release of the KPI feedback survey**
  * The Committee confirmed that the survey was finalised and ready, and agreed that it would be presented at the next Intersect Committee Council before being shared with committee chairs.
* **Review any updates on the Dijkstra hard fork**
  * The Chair confirmed that the Dijkstra hard fork scope and hard fork planning documents had been published following agreement with relevant stakeholders, and highlighted the elements most relevant to the Product Committee.

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