> For the complete documentation index, see [llms.txt](https://public.euroavia.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://public.euroavia.eu/euroavia-documentation.md). # EUROAVIA Documentation


Bylaws	The purpose of the Bylaws is to provide necessary procedures for running EUROAVIA at a European level. The Bylaws, however, also add some additional, more detailed, organizational points when necessary. The proposal for the change of the Bylaws was last voted and accepted by the Congress during AMEAC 2025.		Bylaws
Statutes	Since November 1999, EUROAVIA has been officially registered at the Dutch Chamber of Commerce. The official statutes were set up in Pisa during the AMEAC of 1999. The Statutes outline the purpose of EUROAVIA as a European student association and provide the organizational basis for EUROAVIA at a European level.		Statutes

Bylaws

The purpose of the Bylaws is to provide necessary procedures for running EUROAVIA at a European level. The Bylaws, however, also add some additional, more detailed, organizational points when necessary.

The proposal for the change of the Bylaws was last voted and accepted by the Congress during AMEAC 2025.

Bylaws

Statutes

Since November 1999, EUROAVIA has been officially registered at the Dutch Chamber of Commerce. The official statutes were set up in Pisa during the AMEAC of 1999.

The Statutes outline the purpose of EUROAVIA as a European student association and provide the organizational basis for EUROAVIA at a European level.

Statutes

--- # 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://public.euroavia.eu/euroavia-documentation.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.