> 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/boneyard/copy-of-scope.md). # Copy of Scope Measurement grounded in our Theory of Change Our Evaluation Framework is underpinned by an interactive [**Theory of Change (ToC)**](/evaluation-framework/the-toolbox/theory-of-change.md), co-created by care workers, people receiving support, family members, volunteers, and community members. This participatory process (described in detail on the [*Group Activities*](/evaluation-framework/methods/group-activities.md) page) ensures the ToC reflects a diversity of experiences and aspirations—and that it remains a living tool we revisit and refine. The LOTI pilot in particular helped us sharpen our understanding of the outputs, outcomes, and indicators associated with a commons-based approach. The ToC guides us to: 1. Clarify what we intend to achieve; 2. Map how our activities will get us there; and 3. Define success from the perspectives of both those giving and those receiving care. By making explicit how our initiatives connect to meaningful outcomes and long-term impact, this ToC sets clear boundaries for our evaluation framework and keeps us focused on the change that matters most to our co-op community. {% embed url="" %} Coop Output Dimensions and Outcome Domains {% endembed %} {% hint style="info" %} In the image about the ToC is highlighting the key outputs and outcomes. Guidance on how to use this interactive ToC can be found [here](/evaluation-framework/the-toolbox/theory-of-change/how-to-use-our-interactive-toc.md) {% 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/boneyard/copy-of-scope.md?ask=&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.