> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/wiki/board.md). # Board The members of the Executive Board are jointly responsible for the overall management of the association. The board consists of: * Chair of the Board * Deputy Chair of the Board * Treasurer * 4 Members of the Extended Board (responsible for projects, education, and community) When electing board members, a FLINTA quota of at least 50% must be taken into account in accordance with the statutes. ### Working mode and Board Meetings In accordance with the Articles of Association, the Executive Board meets at least once a quarter. At the beginning of its term of office, the Executive Board agrees on meeting dates for the year; the aim is to hold a monthly meeting on fixed weekdays and at fixed times. These meetings usually take the form of video conferences. In accordance with the Articles of Association, the Executive Board has a quorum if at least half of the current members of the Executive Board, including the Chair or Deputy Chair, participate in the meeting. Resolutions within the Executive Board are passed by majority vote. In the event of a tie, the Chair or, alternatively, the Deputy Chair has the casting vote. The minutes of the Executive Board meetings are public and available to all members upon request. ### Core Team Retreat Once a year, our core team meets to review the year and plan internal projects for the upcoming months. All information about this will be announced in #core-general. {% hint style="info" %} If you are interested in joining the board, please contact us via . Elections for board members take place annually at the general meeting. {% endhint %} --- # 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://docs.correlaid.org/wiki/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 `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.