> 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/care-wealth-in-commons-based-care.md).

# Care wealth in Commons-based care

## Care labour

Typography of care labour ....

## Social Capital

*Caregiving and nurturing actions not only meet immediate needs but also build social capital, enhancing overall well-being. The relatedness, care, generosity, trust, accountability, and belonging that is generated through ongoing care and support, define a kind of "Care Wealth." This resource is primarily generated from within the non-commodified spheres of informal care and support. It is often overshadowed by the financial and physical capital generated through the exchange of goods and commodities in the market. Care Wealth, however, is vital for community well-being and resilience and can lead to these other forms of capital through the sharing of tangible physical and economic resources and assets.*

*Our commons model of care seeks to engage this Care Wealth to enhance people's quality of life within our service. It's also the resource we aim to help generate to strengthen local community networks' well-being and resilience."*

### Value is nested in relaitonships

###


---

# 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/boneyard/care-wealth-in-commons-based-care.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.
