The dietary graph
hello.food keeps diet styles, allergies, health conditions, other restrictions, cuisines, activity, and notes as separate data. It does not stuff your entire dietary life into one giant prompt.
heyfood ask "What should I order given my dietary profile?"Each restriction keeps its source
Profile format v5 records where each restriction came from. That lets clients rebuild combined restrictions and remove one selection without deleting another restriction that still needs the same rule.
{
"selection_provenance_version": 1,
"diet_style_ids": ["low_fodmap"],
"allergy_ids": ["peanut"],
"health_condition_ids": ["ibs"],
"additional_restriction_ids": ["onion", "garlic"]
}Example only. The public catalog includes IDs and broad restriction tags, not the private evaluation engine.
Household members stay separate
The service keeps each member's concerns and results separate. heyfood v0.9.0 uses the signed-in owner's profile. Commands for editing profiles, members, and households are not available yet.
$ heyfood ask "What can I eat?"
$ heyfood item "pad thai at Pismo's"Older clients still work
New clients save the source lists. hello.food rebuilds the older flat fields before preview and upload. Labels from older clients remain in the profile instead of quietly disappearing.
- Catalog changes are versioned, and new entries normally do not break older clients.
- A CI check keeps the published catalogs in sync.
- An empty list means “none selected”; a missing list may mean the profile came from an older client.
- Condition severity remains attached to its selected condition.