> 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/circle-dimensions.md).

# Circle Dimensions

<mark style="background-color:green;">\[MH: NOT SURE DEFINITION OF CIRCLES SHOULD GO HERE? MORE RELEVANT FOR CONTEXT SECTION?]</mark>

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

{% tabs %}
{% tab title="Circle Outputs" %}

* Commons resource circles with volunteers.
* Multi-stakeholder service evaluation measures the social climate, individual well-being and quality of life of Circle members.
* Key roles or "Circle Hats" are nominated by circle members sociocratically.
* Key roles for circles to start and support teams are shared amongst circle members as " Circle Hats".
* Circles resource teams with local volunteers.
* Circles connect teams to local resources and community networks that can enrich the quality of lives of team members.
* Teams are started, supported and ended through local circles.
* Teams are started, supported and ended through local circles.
* Circles operate semi-autonomously from the wider coop with distributed decision-making authority.
  {% endtab %}

{% tab title="Activities (what we did)" %}

{% endtab %}

{% tab title="What we learned" %}

{% endtab %}

{% tab title="Recommendations" %}

{% endtab %}
{% endtabs %}


---

# 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/circle-dimensions.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.
