> 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/parking.md). # Parking Parking is organized to keep the property accessible and safe, and to protect the green areas. ## Guidelines * Park only in the parking area, not on grass or garden areas — the green area of the parking site is maintained by the garden team. * Never block the entrance gate, access lanes, or other vehicles: emergency and delivery vehicles must always be able to pass. * The community electric cars have their charging spots — don't occupy them with other vehicles, and always leave charging access free (see [Car Use](/protocols/community/car-use.md)). * Lock your vehicle and don't leave the engine running unattended. ## Longer Stays and Guests * If you leave a vehicle parked for an extended period, inform the stewards and make sure it can be moved if needed. * Tell your guests where to park before they arrive, and coordinate with the stewards for group arrivals or events. ## Care of the Space * Report oil or fluid leaks immediately — they contaminate the soil. * Don't do vehicle maintenance on the property without checking with the stewards first. If a vehicle is blocking access or you notice any problem in the parking area, contact the stewards. --- # 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/parking.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.