> 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/17th-june-2026.md).

# 17th June 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/1cJMVfs1KJYCPm-kFc28avalsqCvm2y6r/view?usp=sharing).

## Participants

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

## Agenda

* Review outstanding actions and updates
  * confirm meeting logistics
  * review outstanding follow-up items.
* Planning
  * review Quarter 2 summary preparation
  * agree Quarter 3 priorities
  * discuss KPI review roadmap.
* Product research
  * review procurement progress
  * discuss expected timelines
  * agree monitoring approach.

## Updates

* **Review outstanding actions and updates**
  * **Confirm meeting logistics**
    * The Secretary confirmed that the committee meeting time had moved 30 minutes earlier and noted the updated schedule.
  * **Review outstanding follow-up items**
    * The Secretary confirmed that the current agenda would focus on planning and product research, with KPI work remaining an outstanding action.
* **Planning**
  * **Review Quarter 2 summary preparation**
    * The Secretary advised that a Quarter 2 summary would be drafted for review by the Chair and Vice-Chair before being brought back to the Committee for approval.
  * **Agree Quarter 3 priorities**
    * The Committee agreed that Quarter 3 should primarily focus on monitoring product research, progressing KPI work, and operating within the available resources following the unsuccessful budget proposal.
  * **Discuss KPI review roadmap**
    * The Committee discussed completing feedback on the Technical Steering Committee KPI proposals, coordinating with the Growth and Marketing Committee, and continuing work towards refining the KPI framework before considering a future on-chain update.
* **Product research**
  * **Review procurement progress**
    * The Chair reported that approximately seven research proposals were currently expected to proceed, subject to final pricing discussions and contract completion.
  * **Discuss expected timelines**
    * The Committee reviewed the expected delivery timelines for research projects and noted that most work was likely to continue through Quarter 3, with many deliverables expected later in the year.
  * **Agree monitoring approach**
    * The Committee agreed that Quarter 3 should focus on executing contracts, tracking research progress, reviewing interim outcomes where available, and using the completed research to support future funding discussions.

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