> For the complete documentation index, see [llms.txt](https://board.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://board.docs.intersectmbo.org/overview/about-intersect-board.md). # About Intersect Board ## **The Governing Board** The Intersect Board of Directors is the governing body responsible for managing the affairs of Intersect and providing overall oversight and direction for the organization. The Board operates in accordance with the [Intersect ByLaws](https://docs.intersectmbo.org/intersect-knowledge-base/legal/intersects-bylaws) and Intersect's wider governance framework. ## **Board Composition** Intersect's Board is structured to maintain a **majority of member-elected Directors**, ensuring that Intersect members have the primary role in determining the composition of the Board. The exact number of Directors may change over time. Under the Intersect ByLaws, the Board must have at least 3 and no more than 10 Directors. ## **Board Meetings** The Intersect Board meets regularly every month. Board minutes can be found in the section called "Intersect Board Meetings". ## **Meet the Board** You can connect and learn more about our serving Board members [here](/overview/intersect-board-members.md). ## **Contacting the Board** The Governing Board can be contacted via --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://board.docs.intersectmbo.org/overview/about-intersect-board.md?ask=&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 `build a script that syncs our docs to a CMS` 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.