> For the complete documentation index, see [llms.txt](https://handbook.hackalong.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.hackalong.io/patterns/coliving.md).

# Co-Living Patterns

Working together might mean eating together and spending a lot of time with each other. These could be considered as temporary communities, and although it works well when everyone is excited of being part of such, it is easy to fall out of grace.

Washing the dishes, cooking, sharing the food, cleaning the toilets, norms of behaviours that should be widely recognised are often the beginning of the end of a group of people, and the projects might be heavily affected by this physical situation. &#x20;

The co-living patterns are here to help on this fundamental aspect, they are game or processes which aid maximising the benefits of being together, while minimising all the drama that could come with it. These patters are there to avoid having to deal with the eons-old "free-rider" problem


---

# 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://handbook.hackalong.io/patterns/coliving.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.
