> For the complete documentation index, see [llms.txt](https://committees.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://committees.docs.intersectmbo.org/intersect-product-committee/committee-meeting-notes/2024/26th-september-2024-2.md).

# 31st October 2024

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

## Participants

<table><thead><tr><th width="202">Position</th><th width="194">POC</th></tr></thead><tbody><tr><td>Chair</td><td>Saman Michael Far</td></tr><tr><td>Secretary</td><td>Lorenzo Bruno</td></tr><tr><td>Voting seat</td><td>Mike Ward</td></tr><tr><td>Voting seat</td><td>Naushad Fouze</td></tr><tr><td>Voting seat</td><td>Juan Sierra</td></tr><tr><td>Voting seat</td><td>Kyle Solomon</td></tr><tr><td>SME</td><td>Zachary Soesbee</td></tr><tr><td>SME</td><td>Alexandru Dochioiu</td></tr><tr><td>SME</td><td>Bartłomiej Kącicki</td></tr><tr><td>SME</td><td>Maciej Krasowski</td></tr><tr><td>SME</td><td>Neil Davies</td></tr><tr><td>SME</td><td>Ben Hart</td></tr><tr><td>SME</td><td>Fergie Miller</td></tr><tr><td>SME</td><td>Nicolas Biri</td></tr></tbody></table>

## Agenda

* review actions + decisions from last session
* product research budget review

## Updates

* The group continued the work on the research budget by estimating FTEs needs for product research in 2025

## Outcomes & Recommendations

* 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://committees.docs.intersectmbo.org/intersect-product-committee/committee-meeting-notes/2024/26th-september-2024-2.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.