> 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-do-it/methods/our-protocols.md).

# Our protocols

Based on the methodologies shared across the Amigdala Collective, several “**protocols**” have been developed — documents that aim to make Amigdala’s tools and practices explicit, offering a foundation for dialogue and exchange among the various actors involved in a project.

These are not fixed sets of rules, but **living documents**, continuously updated based on experience and the feedback received.

## **Protocol for site- and community specific art practices** 

In 2024, the protocol for **site- and community-specific practices** was created. It is shared with **guest artists** and with all those who engage with the Amigdala ecosystem, to foster alignment around working methods.

{% content-ref url="/pages/UiE8LOdL9tSLmsOteYah" %}
[A sharing of purpose for site- and community-specific art practices](/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/how-we-do-it/methods/our-protocols/a-sharing-of-purpose-for-site-and-community-specific-art-practices.md)
{% endcontent-ref %}

## **Protocol for Territorial Research**

The protocol of the **Territorial Research Group** was drafted in March 2024 as a first shared reflection on the intentions and working methods of the group’s members. It helped define and make explicit the **methodological infrastructure**, enabling it to be shared.\
Through this process of methodological alignment, the group’s purpose and the political mandate of its actions were articulated.

{% content-ref url="/spaces/sFETWEghZLHqmORYed0u/pages/6naPPTvVSLWxUKyTr4tK" %}
[Protocol for Territorial Research](/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/how-we-do-it/methods/our-protocols/protocol-for-territorial-research.md)
{% endcontent-ref %}

<sub><mark style="color:blue;">ph Federica Rocchi, Periferico<mark style="color:blue;"></sub> <sub><mark style="color:blue;"> </sub><sub>*<mark style="color:blue;">Dimore</mark>*</sub><sub><mark style="color:blue;">, R-Nord, Modena 2015<mark style="color:blue;"></sub>


---

# 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-do-it/methods/our-protocols.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.