> 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/scope/mapping-equal-care-outputs-to-outcomes-domains.md).

# Mapping Equal Care Outputs to Outcomes Domains

Our  ToC outlines the sequence of [outputs](https://app.gitbook.com/o/-LAn2M1KHTfeytYv9aib/s/-MN8VA8CjNRwZEdN7ikK/~/changes/541/evaluation-framework/the-toolbox/theory-of-change/using-toc-tool-to-understand-our-model-of-care-key-outputs.) and activities required to achieve all three key outcome domains. These outputs are also grouped, under four key dimensions of our service:&#x20;

* Circles
* Platform
* Teams
* Commons

This structured mapping clarifies how outputs and activities are measured and how they contribute to different outcome domains. It establishes a clear connection between actions (outputs and activities) and their results (outcomes). To highlight theses connections we have separated out these causal chains into distinct service dimensions and their associated outputs and outcomes.&#x20;

Our interactive ToC enables users to focus on the sequence of outputs and outcomes for the Circles, Platform, Teams and Commons dimensions of our service.

### The Circle ToC

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

### The Platform ToC

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

### The Teams ToC

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

## The Commons ToC

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

{% hint style="info" %}
You can use the filters and functions of our interactive ToC to explore these ToC's by following the guidance [here](https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/orientation-to-toc-tool-the-kumu-platform.md). You can alsoclick and drag elements into space in order see their connections more clearly. &#x20;
{% endhint %}


---

# 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/scope/mapping-equal-care-outputs-to-outcomes-domains.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.
