> 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/kitchen/fridge.md).

# Fridge

The fridges are a shared resource that need daily mindfulness and a regular review rhythm to prevent waste and confusion.

## Storing Food

* Label personal perishable food clearly with your name (see [Food Storage](/protocols/kitchen/food-storage.md)).
* Keep personal and community food visibly separate, and respect other people's labeled items.
* Use closed containers for leftovers and label them with a date.
* Let hot food cool down before putting it in the fridge.
* Don't overcrowd the shelves: air needs to circulate for even cooling.
* Close the door promptly and check that it seals well.

## Review Rhythm

Following the [Cooking](/protocols/kitchen/cooking.md) and [Food Storage](/protocols/kitchen/food-storage.md) protocols:

* Once a week the kitchen-cooking responsible organizes a review of the food in the fridge and gets rid of moldy, wasted, or expired food.
* Plan purchases so expiration dates fall around the new moon (roughly every two weeks).
* The fridges are emptied and cleaned at the end of every lunation, as part of the last lunation clean-ups.

## Cleaning

* Clean spills immediately so they don't stick or smell.
* For the lunation-end clean: empty the fridge, remove shelves and drawers, wash with warm soapy water, dry, and put everything back organized.

## Report to the Stewards

* The fridge not cooling properly or making unusual noises
* Water pooling inside or underneath
* A door that doesn't seal

A tidy fridge means less wasted food and a nicer kitchen for everyone.


---

# 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/kitchen/fridge.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.
