> For the complete documentation index, see [llms.txt](https://play.equal.care/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc.md).

# How to use our interactive ToC

Navigating the Theory of Change: A Quick Orientation

Our interactive Theory of Change (ToC) is built using [Kumu](https://kumu.io), a tool that lets us map and explore how different parts of our model connect to the outcomes we want to achieve. This interactive map helps make sense of the relationships between activities, outputs, and the broader changes we’re working toward.

You can use the map to follow specific themes (like teams, commons, or the platform), see how different goals are linked, and dig into outcomes and indicators. The pages that follow show you how to navigate the map, filter and focus the view, and explore what matters most to you.

If you’d like to adapt our Theory of Change for your own organisation, you can create a personal copy of the map using Kumu’s "duplicate" feature (known as “forking”). We’ve included a guide on how to do that too.

{% embed url="<https://embed.kumu.io/e2a346efcd5e211132a02cce89d4a693>" %}

To open this ToC view in a separate window in your browser click [here](https://embed.kumu.io/e2a346efcd5e211132a02cce89d4a693)

{% hint style="info" %}
Before using and navigating our interactive ToC it can be useful to understand the basic architecture of Kumu (the interactive mapping platform) and the take a look at the curated ToC views and explanations in the following pages. These pages help you navigate our ToC map, providing a deeper understanding of the different dimensions of our service and their connections to the impacts we are seeking to achieve.&#x20;
{% endhint %}

Step 2. Deeper dive into Coop Service Dimensions

{% embed url="<https://embed.kumu.io/4ed68d307fde05b117bd900007884b35>" %}

Step 3. Deeper dive into Coop Outcomes Domains

{% embed url="<https://embed.kumu.io/9a6b333e18ad31ef8a4243e81e6ad121>" %}


---

# 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://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc.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.
