> For the complete documentation index, see [llms.txt](https://wiki.oikos-international.org/oikosmos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.oikos-international.org/oikosmos/oikos-initiatives/community-in-action/legislative-meetings-mandatory.md). # Legislative Meetings (mandatory) The Legislative Meeting (LM) is hosted by oikos International twice a year (April & October). It is a space where important decisions are taken that have an influence on oikos International as the umbrella organization of oikos, as well as on the community at large. With our legal form as a Swiss association, it is necessary that our members (aka FULL chapters) democratically take certain decisions within the LMs. Each full chapter can send one representative to vote on behalf of their chapter, though any oikee is welcome to join the meetings (though without voting).\ Furthermore, Legislative Meetinga are a space to connect with other chapters and receive important updates you can take back to your chapter. **You will always receive the latest information about the upcoming LM in your oikos chapter inbox, so make sure to check it regulalry!** Depending on our possibilities, the meetings happen onsite (hybrid) or fully online. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.oikos-international.org/oikosmos/oikos-initiatives/community-in-action/legislative-meetings-mandatory.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.