> 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-membership-community-committee/committee-meeting-notes/2024-meeting-minutes.md).

# 2024 Meeting Minutes

Here are a few notes on how to read the proceedings of the Membership and Community Committee. 

* Each agenda item is separated into two sections. 
* The text before "outcome" includes the intentions and reference info for the agenda item. 
* The text below "outcome" includes info provided to the committee by the item lead, points of ensuing discussion, decisions made, and actions authorized. 
* Be aware - As we begin to publicize these notes and sand down the rough edges, we ask for your feedback to help improve our communication. However, these documents are not edited for external comms. They are an unfiltered operational record for the committee.

1. [August 20th](https://docs.google.com/document/d/1wfpX_N_9IBkj0MiQRW2-1lk-PCHfBnHjEn-mck3DpuE/edit?usp=drive_link)
2. [August 13th](https://docs.google.com/document/d/1B8QBqCLvC54ciSRPwish_DBg1REn4sBW9pkVqaF34Yw/edit?usp=drive_link) 
3. [August 6th](https://docs.google.com/document/d/1hPEAoWyV5FdMFVHuHqMQV17-TTidBXetdPJbzfG3mBU/edit?usp=drive_link)
4. [July 30th](https://docs.google.com/document/d/1FD9xTG1RDMiupxw7PbgveSoMTDXdJZL7jwNJOul3WnA/edit?usp=drive_link)
5. [July 23rd](https://docs.google.com/document/d/1-gppD4XbBgN8a1UToZuGsmGLNrOH0oZhzPUAeiV9HnI/edit?usp=drive_link)
6. [July 16th](https://docs.google.com/document/d/1WLakdyMyOr4IM7PxhZlcBRwk7bJHbLieRwKNErreLjY/edit?usp=drive_link)
7. [July 9th](https://docs.google.com/document/d/1thuvvAgvgQyD1iXUMieiTUM0-zsWXz0VR1GBGdC41mM/edit?usp=drive_link)
8. [July 2nd](https://docs.google.com/document/d/1iCRRVUcG3ZiyNdOfxY-46tyyAhJpL0k_S11bwS_vj6s/edit?usp=drive_link)
9. [June 25th](https://docs.google.com/document/d/10n9ttzl3hD_ciexqjsnfdfYsJXxPLzVT0-JK2jch65E/edit?usp=drive_link)
10. [June 18th](https://docs.google.com/document/d/1zifnQJFv6Het43DmTWzuTVfoT-cPKIhpHS66475dv5U/edit?usp=drive_link)
11. [June 11th](https://docs.google.com/document/d/1_eXeEHPUhWaeKjvIPMMupi3On_hmATJz5eYWrDmWI8Y/edit?usp=drive_link)
12. [June 4th](https://docs.google.com/document/d/1nzCZCKFhwSrjPkdrnnFnVnTUMaXZkO_oFjOBlVbhT2E/edit?usp=drive_link)
13. [May 28th](https://docs.google.com/document/d/1bTyvo1qqrB30a0ql0M27on77XLupyC7rm_0HdrnUP88/edit?usp=drive_link)
14. [May 21st](https://docs.google.com/document/d/1yELxeIJq0AqajCcyZbLVa0xFS3WG8McQdNXyiW0iC_k/edit?usp=drive_link)
15. [May 14th](https://docs.google.com/document/d/1hp3B5i0xpNovuT-BiBRLeU-Kjj2qyXSZuuTalxkRajg/edit?usp=drive_link)


---

# 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-membership-community-committee/committee-meeting-notes/2024-meeting-minutes.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.