# INVENTORY — kitchen, premade portions, ratings

The log is not only “what I just ate.” The kitchen is a first-class object.

## Items

- Ingredient (butter, eggs, a joint of lamb) **or** premade meal (Saturday stew, 4 portions)
- Quantity or **portions remaining**
- Status: available → eaten / unavailable / rotten / discarded
- Optional cooked-on / use-by. Rotten is a user mark (or an obvious date). The coach **asks**, it does not silently delete.

## Premade meals

- Snapshot ingredients + nutrition + cooking fat at cook time
- Eating portion 3 next Thursday must **not** re-guess
- Linked recipe (the method), which can be cooked again
- Eating a portion: decrement, write a meal log from the snapshot, almost no AI cost

## Recipes

- One recipe = one markdown-shaped document
- Seed set in `RECIPES.md`, then user recipes from “I cooked this”
- **Ratings** per cook: good?; what was missing?; too dry?; would make again?
- Ratings feed the coach as suggestions, not assignments

## Prototype

A markdown `inventory.md` per user is enough to mock this. No barcode fortress, no warehouse management system.