> For the complete documentation index, see [llms.txt](https://docs.liminalvillage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liminalvillage.com/protocols/common-spaces/patio.md). # Patio The patio is a central outdoor space for shared meals, socializing, and relaxing. Like all common spaces, it should be left as you found it — or better. ## Using the Patio * Clean up right after meals: clear all dishes and cups, wipe the tables, and take rubbish to the bins. * Return chairs and furniture to their usual arrangement after use. * Don't leave food out — it attracts insects, roaming cats, and other animals. * Be considerate with noise, especially in the evening: sound carries far outdoors. * No shoes rule doesn't apply outside, but avoid entering the house with wet or dirty feet (see [Pool Use](/protocols/common-spaces/pool-use.md)). ## Weather * **Wind**: secure or bring in cushions, papers, and lightweight items — the same care as for the [Pagoda](/protocols/common-spaces/pagoda.md). * **Rain**: bring fabric items inside and check nothing is left out that shouldn't get wet. * **Sun**: use the shade available and put back whatever you move. ## Maintenance * Sweep the patio when leaves and debris accumulate. * The yard and tiles get a weekly cleaning as part of the [Gardening](/protocols/gardening/gardening.md) routine — join in. * Report broken furniture or lights to the stewards. The patio is often the first space guests experience — let's keep it beautiful and inviting. --- # 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://docs.liminalvillage.com/protocols/common-spaces/patio.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.