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

# 8th 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/1_yovCjX7JGCmhcwXT6IeAyGfWkOzhjQn/view?usp=sharing).

## Participants

| Name                    | Role                               | Attendance |
| ----------------------- | ---------------------------------- | ---------- |
| Samuel Leathers         | Chair                              | Yes        |
| Lorenzo Bruno           | Secretary                          | Yes        |
| Alexandre Maaza         | Voting Seat (Vice-Chair Appointee) | Yes        |
| Juan Sierra             | Voting Seat                        | Yes        |
| Yoram Ben-Zvi           | Voting Seat                        | Yes        |
| Alexa C. (Thyme Studio) | Voting Seat (Vice-Chair)           | Yes        |
| James Meidinger         | Voting Seat                        | No         |
| Christian Schmitz       | Voting Seat                        | No         |
| Giorgio Zinetti         | Voting Seat                        | No         |
| Samir Idris             | Voting Seat                        | Yes        |

## Agenda

* Review actions and updates
  * Updates on product research
* Product research
  * Prepare X post contingent on contract execution
  * Secretary to prepare draft post
* Review KPI document from TSC
  * Review proposed KPI changes and current status (in Miro)
  * Agree feedback for TSC

## Updates

* **Review actions and updates**
  * **Updates on product research**
    * The Secretary confirmed that the Committee had approved the research funding recommendations, notified all applicants of the outcome, published the evaluation report and successful proposals, and commenced procurement, KYC/KYB and contract preparation activities.
    * The Committee also welcomed Alexa C. (Thyme Studio) as the newly appointed Vice-Chair following the completed committee vote.
* **Product research**
  * **Prepare X post contingent on contract execution**
    * The Secretary proposed publishing an announcement summarising the successful research proposals once contract execution is complete, and the Committee agreed that the communication should explain the funded research themes and acknowledge the return of unused treasury funds.
  * **Secretary to prepare draft post**
    * The Secretary agreed to prepare a draft X post for Committee review before publication.
* **Review KPI document from TSC**
  * **Review proposed KPI changes and current status (in Miro)**
    * The Committee reviewed the proposed KPI amendments from the Technical Steering Committee, discussed replacing transaction-based metrics with protocol revenue metrics, questioned the assumptions supporting the proposed growth targets, and agreed that further clarification from TSC was required before finalising feedback.
  * **Agree feedback for TSC**
    * The Committee agreed to consolidate its questions and discuss them with the Technical Steering Committee before providing final feedback on the proposed KPI changes.

## Outcomes & Recommendations

N/A

## Decisions Recorded

Product Research funded proposals approved on Member Area Vote <https://members.intersectmbo.org/dashboard/voting/50/event-results>


---

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