Eating
In plain words: Wellbeing: meal planning
How Wellbeing plans meals from restrictions, available food, time and equipment, with strict hard-constraint checks and minimal handoffs to Homestead.
- 1Candidates are blocked, unresolved or eligible; never labelled safe.
- 2Unknown quantities stay unknown; units convert only with sourced data.
- 3Only an explicit check-in confirms what was eaten.
Words on this page, decoded click one for its card
A cupboard can contain ingredients without containing a feasible meal. Eating turns reviewed restrictions, available food, time, and equipment into choices the MagusYou, the Operator can edit, approve, or reject. It also provides preparation guidance; a suggestion records neither cooking nor consumption.
Plan under hard constraints
The food mode of wellbeing.plan_cycle@1 pins profile, consent, policy, PatternWorkflow, reviewed food catalogue, tools, provider, and any InventorySnapshot@1. Deterministic checks traverse ingredients to a finite depth and classify each candidate as blocked, unresolved, or eligible. The interface never translates eligible into “safe.”
An unknown package quantity stays unknown. Decimal arithmetic preserves dimensions; volume becomes mass only through sourced ingredient-specific density. Serving, 100 g, and whole-package bases remain distinct. Neither a model nor a convenient recipe may invent identity or quantity to make the arithmetic close.
Exclusions, equipment, time windows, and operator maxima are hard gates. Variety, convenience, and cost influence the remaining choices. When no choice passes, the result is no feasible plan. Eating does not certify kitchen cross-contact or medical safety.
Minimal Homestead handoff
Stores supplies only the food identity, quantity interval, location class, freshness or expiry evidence, storage-condition uncertainty, and provenance in InventorySnapshot@1. Whole receipts, credentials, payment, addresses, and unrelated stock remain at home with their owner.
If an approved plan lacks ingredients, send only what Provision needs in FoodNeed@1: quantities, declared exclusions, useful product traits, expiry, privacy class, and unresolved flags. Keep diagnosis, journal, measurement, medication, genetics, movement history, and merchant instructions out of it. When ProvisionResult@1 returns, Eating uses its availability evidence to decide whether the plan still fits.
After the meal, only an explicit wellbeing.check_in@1 can confirm eating or substitution and send a minimal consumption event for stock reconciliation. A purchase, recipe, prepared household lot, plan, or silence cannot establish what the person ate. Eating itself never sources products, mutates stores, builds carts, or pays.
Return to Wellbeing.