> For the complete documentation index, see [llms.txt](https://handbook.collettivoamigdala.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.collettivoamigdala.com/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/how-we-organize-ourselves/meetings-and-documentation.md).

# Meetings & documentation

<details>

<summary>Contents of this page</summary>

* [Meetings](#meetings)
  * [Meeting Template](#meeting-template)
* [Documentation](#documentation)

</details>

## Meetings

Meetings are a crucial moment for building shared understanding, exploring ideas, and making decisions.\
To ensure that every voice is heard and that discussions are inclusive and productive, we use **speaking rounds**. This method allows all *compagne* to express their thoughts and concerns in a respectful and structured environment. Speaking rounds foster **equity and effectiveness** in collective processes.

Meetings are **facilitated by a facilitator**, whose role is to support active and inclusive participation, while keeping the group focused on the meeting’s objectives. The facilitator ensures that time is used efficiently and that discussions remain relevant and constructive.

At the end of each meeting, a **summary of key points and decisions** is shared, ensuring that all members are aligned on outcomes and next steps.

Each group defines the **rhythm and timing** of its own meetings.

### Meeting Template

{% embed url="<https://docs.google.com/document/d/1I2e8g5LVCSRcNbzMGQB5V51utwcewlIWlmJwpyRlEDc/edit?tab=t.0#heading=h.xzlztc81gd4j>" %}

## Documentation

To promote **transparency and accessibility**, each group — and especially the *scribe* — is responsible for keeping clear its policies, meeting’s notes, and all key documents and information in the group’s shared **Drive folder**.\
This ensures that every *compagna* has access to the documentation of both the groups she belongs to and those she does not, fostering an open and informed organisational culture.


---

# 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://handbook.collettivoamigdala.com/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/how-we-organize-ourselves/meetings-and-documentation.md?ask=<question>&goal=<user_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.
