Margaret’s daughter, on a recent visit to Sacramento, opened her mother’s refrigerator and recognized very little in it. The dietary changes had not been announced. They had emerged across nine months: more fish, less red meat, a shift to whole grains, the disappearance of canned soups, the appearance of low-sodium versions of items Margaret had bought in their familiar versions for forty years. The daughter recognized the result as the cardiologist’s recommendations finally being followed. She did not know how. Margaret had never managed her diet by rule. She cooked what she liked from what was in the kitchen. Yet what was in the kitchen had changed.
The nutrition concierge is what changed the kitchen. Not by issuing instructions Margaret would have to follow. By coordinating with the buying agent that purchases the groceries, with the health concierge that holds the dietary restrictions, with the cognitive concierge that knows what mental load is reasonable on a given day, and with the social concierge that recognizes meals as social acts. The result is that what arrives in the kitchen is consistent with the dietary guidance, while what Margaret cooks remains hers.
Nutrition spans health, buying, culture, preference, and social eating, which is why it is a separate concierge agent rather than a feature of the health concierge. The dietary restriction from health informs the meal plan. The meal plan drives procurement through buying. The cultural and personal preferences shape what the meal plan can prescribe. The cognitive state determines whether a complex recipe is appropriate today or whether tonight’s dinner should be the simple pasta dish that does not require sustained attention. One concierge holds these threads. None of the others could.
Why nutrition is not a health feature#
The naïve architecture would make nutrition a function of the health concierge. The health concierge holds the dietary restrictions, after all, and dietary intake affects health outcomes. The argument seems straightforward.
It fails on closer inspection. The health concierge’s frame is clinical: medication, vital signs, symptoms, appointments, transitions between care settings. Nutrition fits into that frame poorly because most of nutrition is not clinical. Most of nutrition is cultural, social, economic, and pleasurable. Margaret’s Wednesday cooking class with the student in Brisbane is a nutrition event. So is her grocery list, her decision to invite a neighbor for dinner, her management of her budget, her cultural preference for ingredients she grew up with, her grandson’s allergy, her cognitive capacity to plan three days of meals on a Sunday afternoon. None of this is clinical. All of it is nutrition.
A separate concierge is the structural acknowledgment that nutrition’s frame is its own. The nutrition concierge can absorb the clinical input from the health concierge as one of several inputs without making the nutrition domain a sub-domain of health. The reverse architecture (nutrition as a feature of health) would either neglect the non-clinical dimensions of nutrition or smuggle non-clinical concerns into a frame that was not designed for them. Both are worse outcomes.
The architectural lesson generalizes. Decomposition follows the contour of the user’s life, not the contour of the technical capabilities that compose to serve it. Nutrition, financial concierge, social connection, and home environment are all examples of agents whose existence is justified by the user’s experience of the domain rather than by a technical capability boundary.
The Nutrition Tracker and the SLM stack#
The nutrition concierge composes from a single primary infrastructure agent (the Nutrition Tracker, 0.5 autonomy, edge deployment) plus shared services from the buying agent, the cognitive concierge, and the family coordination concierge.
The Nutrition Tracker maintains the structured nutrition context: dietary restrictions and their sources (cardiologist for sodium, endocrinologist for carbohydrate timing, allergist for the shellfish allergy, personal preference for the vegetarian shift Margaret made in 2018), cultural and personal food preferences (the brands and ingredients she has used for decades, the dishes that mean something to her family), cooking ability and energy patterns (Sunday afternoons are good for batch cooking, Tuesday evenings she usually wants something simple, Saturday mornings she might cook with her granddaughter on video call), and intake patterns over time (what she actually eats, inferred from grocery purchases, restaurant orders, and what she reports when the agent asks).
The Nutrition Analyst SLM runs at 100M parameters and targets under 75ms inference. Its job is to compose meal plans against the constraint set, generate recipe suggestions, evaluate substitutions for dietary compliance, and answer questions Margaret asks about nutrition. The model is deliberately small because most nutrition reasoning is structured: lookups against ingredient databases, application of rule-based dietary constraints, simple optimization across a constrained menu. The complex reasoning happens elsewhere: the Response Generator handles conversation, the MoC Router (Series 02) handles context selection, the Safety Filter screens output. The Nutrition Analyst itself does not have to be large. The 100M is enough.
This pattern repeats across the system. Concierge-specific SLMs are sized to their tasks. Specialized models are small because their tasks are tightly scoped. The shared models (Response Generator at 400M, Cognitive State Estimator at 200M) are sized to the harder tasks of conversation and inference. The architecture is parsimonious about parameter count because parameter count is what determines whether the system runs on consumer hardware in the Margaret-on-her-tablet scenario or requires constant cloud round-trips. Edge feasibility is a design constraint, not an aspiration.
Dietary constraint integration#
The cardiologist updated Margaret’s sodium restriction from 2,000 mg/day to 1,500 mg/day on a Tuesday. By Tuesday evening, the nutrition concierge had updated the meal plan, the buying agent had adjusted the grocery list, and the family coordination concierge had updated the daughter’s view of the household nutrition picture (with Margaret’s consent, configured to share dietary changes with family without sharing the reason for them; Margaret has chosen to disclose the reason herself if and when she chooses).
The integration is the architecture in one example. The dietary update did not require Margaret to do anything. The cardiologist wrote it into the FHIR record. The health concierge’s read picked it up. The health concierge propagated the constraint to the nutrition concierge. The nutrition concierge ran its constraint solver against the existing meal plan and produced an updated plan that maintained Margaret’s preferences and cultural patterns while reducing sodium to the new target. The buying agent received the updated plan and adjusted the grocery list. By the time Margaret noticed any change in her kitchen, the change had already been made.
The constraint solver is structurally interesting. Margaret’s dietary constraints are partial, weighted, and sometimes contradictory. The hard constraints are non-negotiable: no shellfish (allergy), no MAOI-incompatible foods (medication interaction). The soft constraints are weighted: low sodium (clinical, recently changed), low added sugar (clinical, longstanding), high fiber (clinical, longstanding), affordable (financial, ongoing), culturally meaningful (personal, ongoing), familiar (personal, weighted lower than the others on most days but higher on cognitive low-capacity days), prepared from ingredients she enjoys cooking with (personal, longstanding). The solver does not produce one optimal meal plan. It produces a feasible plan that respects the hard constraints, satisfies the high-weight soft constraints to a reasonable degree, and surfaces tradeoffs for Margaret’s review when the constraint set becomes infeasible.
The infeasibility cases are instructive. When the new sodium restriction made several of Margaret’s longstanding favorite dishes infeasible at the previous preparation, the solver did not silently remove them. It surfaced the tradeoff: “The chicken cacciatore as you usually prepare it has 1,400 mg of sodium per serving. With reduced sodium broth and reduced sodium tomato paste, it would be 750 mg, with some change in flavor that you might or might not notice. Would you like me to try the modified version this week?” Margaret said yes. The modified version worked well. The dish stayed in rotation. A different person might have said no and chosen to retire the dish from rotation in exchange for keeping the original recipe for the rare occasions when the higher sodium fit her overall day’s intake. Either choice is hers.
Cultural food preferences#
The agent’s most underdeveloped capability today, in mid-2026, and one of its most important. Most nutrition guidance in the United States is built against an implicitly Anglo-American cultural baseline. The dietary advice that works for a person whose meals revolve around bread, salad, and grilled protein does not translate cleanly to a person whose meals revolve around rice, beans, and stewed vegetables. Or to a person whose meals revolve around dumplings, congee, and pickled side dishes. Or to a person whose meals revolve around couscous, harissa, and lamb. The agent’s cultural awareness is the difference between guidance that the person can follow and guidance that asks her to abandon her own culinary tradition.
The agent maintains a structured representation of the person’s cultural food context: regional traditions, family recipes, ingredient preferences, religious or ethical eating patterns (kosher, halal, vegetarian for Hindu families, fish on Fridays for Catholic families, fasting practices). The constraint solver respects these as soft constraints with high weights. The grocery list is shaped by them. The meal suggestions emerge from them. The architecture’s job is not to convert Margaret’s eating into something the model thinks is healthier; it is to support Margaret in eating well within her own tradition.
The honest limitation: the depth of cultural representation today is uneven. The system has good coverage of major U.S. immigrant traditions where the user population is large enough to have produced a meaningful training signal. It has weaker coverage of smaller diaspora communities, of regional variations within larger traditions, of family-specific preferences that diverge from a tradition’s typical pattern. The agent’s response in these cases is to defer to the person’s expressed preferences rather than impose a model-derived assumption. The system that pretends to understand a tradition it has not really learned is the system that produces alienating recommendations. The architecture chooses honest deferral over false confidence.
Meal planning as cognitive support#
A pattern that emerges across users with mild cognitive change. The structured rhythm of meal planning, grocery shopping, and cooking is itself a cognitive scaffold. The person who knows that Tuesday is fish night, Wednesday is pasta, Thursday is the farmers’ market, Friday is leftover night has a structure that supports executive function. The person whose week has no rhythm has a more fragile cognitive footing.
The nutrition concierge supports this rhythm without imposing it. Margaret can declare a weekly rhythm if she wants one. The agent maintains it, surfaces it gently when she might be drifting from it, and helps her recover the rhythm after a disruption (the visit from the daughter, the week she was unwell). The agent does not enforce the rhythm. The rhythm is Margaret’s. The agent’s contribution is making it easier to maintain.
This is one of several ways the nutrition concierge supports the cognitive concierge’s work. The integration runs in the background. Margaret never says to either concierge “please help me maintain my rhythm.” The integration emerges from the shared context model and the agents’ coordinated responses to her observed state.
Grocery integration with the buying agent#
The most operational integration in the architecture. The nutrition concierge produces the meal plan. The buying agent procures the groceries. The two agents share the structured meal plan as data, not as message. There is no API call that says “buying agent, please buy these items.” The meal plan is in the shared context. The buying agent reads it on its scheduling cycle and adjusts the grocery list accordingly.
The integration handles edge cases. When the meal plan calls for an ingredient that is unavailable at Margaret’s preferred grocery vendor, the buying agent surfaces the substitution to the nutrition concierge before placing the order. When the price of an ingredient has spiked beyond the meal plan’s cost target, the nutrition concierge can suggest a recipe substitution rather than the buying agent simply buying the more expensive ingredient. When Margaret has indicated she will be eating with her granddaughter on Saturday, the meal plan adjusts and the buying agent picks up enough for two.
The next article addresses the earning concierge: the agent that helps people who want to continue contributing economically navigate the discovery, logistics, and cognitive protection challenges of doing so.
Cross-References#
Eating Well, Living Well (BML-01 series, nutrition subsections). The editorial framing of nutrition from the user’s perspective, including the human texture of dietary change that the architecture supports.
The Health Concierge (BMT-01.02). The source of dietary restrictions that flow into the nutrition concierge’s constraint solver, including the FHIR-driven integration that makes constraint updates automatic.
The Buying Agent (BMT-01.03). The related concierge that procures the groceries against the meal plan, demonstrating the cross-concierge integration that no standalone app could replicate.
The Cognitive Concierge (BMT-01.07). The agent whose state assessment shapes how complex a meal plan is appropriate for a given day and whose dignity constraints the nutrition concierge inherits.
Technical Appendix BMT-01.10-A is available to partners and investors at partners.bluemirror.tech.