> 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/miscellaneous/bylaws-subpages/1-introduction.md).

# 1 Introduction

### 1.1 EUROAVIA

EUROAVIA, the European Association of Aerospace Students, is a European based students’ initiative whose main fields of activity are aerospace, engineering and the adjacent fields. The goals of EUROAVIA are:

1. To promote European cooperation in the aerospace field by providing opportunities for its members to meet, exchange and learn at all levels.
2. To internationally represent European aerospace students.
3. To acquaint student members with their future working environment stimulating contacts with the industry.

As stated in the Statutes, we might refer to EUROAVIA as “the Association”.

### 1.2 Membership and structure

The Association is formed by ordinary and non-ordinary members:

* Ordinary members, called as Affiliated Societies (AS), are local, Europe-based, incorporated associations of students interested in the aerospace sector, acting under the name of EUROAVIA, which have applied for membership with the Board of the Association, and which have been admitted as ordinary members of the Association by the General Meeting.
* Non-ordinary members, called as Adjunct Members (AM), are local, non-Europe-based, incorporated associations of students interested in the aerospace sector, acting under the name of EUROAVIA, which have applied for membership with the Board of the Association, and which have been admitted as non-ordinary members of the Association by the General Meeting.

Prospective members enrolled in the procedure of acquisition of the full membership will be named Prospective Affiliated Societies (PAS) and Prospective Adjunct Member (PAM).

Refer to chapter 2 for further information.

The structure of the Association is composed by four main organisms:

1. The Local Groups (LG), that include all (P)AS/(P)AM within EUROAVIA.
2. The Working Groups (WG), defined in the chapter 5.7 of the Bylaws.
3. The International Board (IB), defined in the chapter 5.2 of the Bylaws.
4. The EUROAVIA Congress, defined in the chapter 5.1 of the Bylaws.
5. The Committees, defined in the chapter 5.7 of the Bylaws.

### 1.3 Bylaws

The purpose of the Bylaws is to provide necessary procedures for running EUROAVIA at an international level. This document, however, also adds some additional, more detailed organisational points if necessary.

### 1.4 Policies

The EUROAVIA policies are formal documents that describe a set of rules, responsibilities, processes, and timelines that dictate the Association´s actions towards a specific topic.

The EUROAVIA policies are:

1. Data Protection Policy;
2. Harassment Policy;
3. Corporate Identity.

For a change in an already accepted policy to be implemented, it must be presented and voted in the General Meeting with a simple majority. If a policy is implemented for the first time, voting shall only be done on the change in bylaws implementing the policy.


---

# 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://public.euroavia.eu/miscellaneous/bylaws-subpages/1-introduction.md?ask=<question>&goal=<endgoal>
```

`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.