> 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/1.-outputs-dimensions-and-outcome-domains.md).

# 1. Outputs Dimensions and Outcome Domains

To make sense of the many activities and goals within our model, we’ve grouped our outputs and outcomes into core dimensions and domains.

* **Output Dimensions** represent the key areas of work across the co-op.
* **Outcome Domains** describe the kinds of change and impact we’re aiming for.

🧭 In this view of our Theory of Change, you can see:

* **Four key output dimensions**:\
  🟧 Teams, 🟨 Circles, 🟦 Platform, 🟩 Commons
* **Three core outcome domains**:\
  🔻 Growth, Well-being, Community & Belonging, Systems Maintenance & Co-production

🔍 Explore the map below to see how these clusters link together.

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

In the following pages, we’ll walk through each of these dimensions and domains, unpacking how specific activities and outputs contribute to our broader goals for care, community, and co-operation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://play.equal.care/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/1.-outputs-dimensions-and-outcome-domains.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.