> 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/3.-coop-outcomes-domains.-a-deeper-dive..md).

# 3. Coop Outcomes Domains. A deeper dive.

This view in our Theory of Change (ToC) brings together the **three key domains of outcomes** we aim to foster across our co-operative model:

**🌱 Growth**

Outcomes in this domain reflect our ambitions to **scale up with integrity**—reaching more people while remaining rooted in our values. These include expanding community capacity, increasing the abundance of care, and growing co-operative membership.

**💞 Well-being, Relationships & Belonging**

This is the heart of our work. These outcomes reflect the **human and relational** dimensions of care: connection, safety, dignity, mutual support, and emotional well-being. They span everyone involved in our services—people giving and getting support, families, volunteers and staff.

**🔧 Systems Maintenance & Co-production**

This domain focuses on the **structures and behaviours** that help Equal Care remain sustainable, participatory and just. Outcomes here relate to collaborative decision-making, peer governance, and maintaining the systems that enable learning, problem-solving and participation.

*👇 Explore the map below to see how each domain contains clusters of related outcomes, and how they link to our broader Theory of Change.*<br>

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

{% hint style="info" %}
You can click on each outcome to explore its description, related outputs, and indicators for measuring progress.
{% 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/the-toolbox/theory-of-change/how-to-use-our-interactive-toc/3.-coop-outcomes-domains.-a-deeper-dive..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.
