Several ways in, one review standard
Use quick add for a single correction. Use camera or gallery capture for pantry shelves, the fridge, freezer, or a grocery haul. Receipt photos follow a distinct purchase path. Image batches stay ordered and are limited to ten files, with temporary bytes deleted after commit or discard.
Extraction creates a draft. The review shows uncertain names, amounts, units, locations, categories, merge choices, and source context before Food changes.
Household language stays in charge
Locations and categories are not hard-coded enums. A household can use “garage freezer,” “snack drawer,” or another real-world name without waiting for a schema migration.
Aliases help familiar wording resolve to the same ingredient while subtype-sensitive foods remain separate. The system should never turn an uncertain similarity into an automatic merge.
Quantity edits carry context
A confirmed quantity update writes value and unit together and records when it was last confirmed. If Chef performs a safe inventory write, the change is audited and can be undone only while later dependencies have not locked it.
That makes quantity useful for recipe fit without pretending every household package is measured perfectly.
Food connects to the next action
Recipes use backend-authoritative ingredient fit to show covered, missing, and check-first evidence. Groceries can consolidate confirmed gaps. After a shop, a put-away review moves purchases into Food; after cooking, cleanup can record what materially changed.
The point is not a beautiful static list. It is a reliable handoff from what the kitchen has to what the household does next.