> 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/why-we-exist/theory-of-change.md).

# Theory of Change

Designing your ToC means **intentionally defining a desirable perspective of change for your reference context**, in the medium to long term, and understanding your differential contribution to achieving that envisioned future. Starting from your areas of action (impact dimensions) and moving to concrete actions taken immediately. Amigdala designs its strategies and sets its practices through the methodological principles and logical framework of the **Theory of Change** (ToC), an established approach in the literature, also quoted and recognized by the Reform of the Third Sector and its Guidelines for the evaluation of social impact.

To delve deeper and read the ToC and impact assessment of the 2022 Periferico festival edition, you can consult the report [here](https://collettivoamigdala.com/wp-content/uploads/2023/10/amigdala-report_impatto-interattivo-1.pdf).&#x20;

<sub><mark style="color:blue;">ph Futura Tittaferrante<mark style="color:blue;"></sub> <sub><mark style="color:blue;"> </sub><sub>*<mark style="color:blue;">Elementare</mark>*</sub> <sub><mark style="color:blue;"> </sub><sub><mark style="color:blue;">di Collettivo Amigdala, Fondazione Pietà dei Turchini, Napoli Altofest 2018<mark style="color:blue;"></sub><br>

{% content-ref url="/pages/twbeie7Z9ho1QP7lpxIB" %}
[Our vision](https://handbook.collettivoamigdala.com/accordi-valori-metodi.-lhandbook-di-amigdala/agreements-values-methods-eng/why-we-exist/theory-of-change/our-vision.md)
{% endcontent-ref %}


---

# 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/why-we-exist/theory-of-change.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.
