Use case · Meals & Groceries

A week of meals — from prompt to plate.

How Aule handles meal planning end-to-end — household preferences plus calendar plus budget plus delivery via Instacart, Kroger, or Whole Foods, with the approval gate before the order ships.

Last updated · 2026-05-19

TL;DR

The household tells Aule what the week looks like. The layer returns a meal plan that respects what it has learned (allergies, weekday cooking time, what worked last week). The grocery order is built, priced, and presented for confirmation. The household approves; the order ships; the loop closes with a receipted summary. The next week, the plan starts from what worked.

Scene one

Sunday evening — the prompt.

The actual scene. The household says something like: “plan dinners this week, the kids have soccer Tuesday and a sleepover Friday.” That is the entire input. Nothing about who is allergic to what, nothing about the new gluten-light kindergarten protocol, nothing about how Wednesday is the night the dishwasher repair window is open. The layer already holds those.

The prompt is the whole conversation. The household does not write a meal-planning brief. The layer does the translating.

Scene two

Monday morning — the plan.

By the time the household checks back, the layer has the week ready.

The McCloud household, week of May 19

Week of Monday, May 19

$182

est. groceries

Tuesday is taco night (portable for soccer-night cleanup). Friday is salmon with provisions left for the sleepover Saturday morning. Wednesday is the dishwasher window — pasta keeps the kitchen quiet.

Monday1 meal
- Dinner
  Roast chicken with sheet-pan vegetables
  Leftovers route to Thursday.
  ×4
Tuesday1 meal
- Dinner
  Beef tacos with cilantro slaw
  Soccer night — built to travel.
  ×4
Wednesday1 meal
- Dinner
  Pasta with roasted tomato and burrata
  Quiet kitchen for the dishwasher repair.
  ×4
Thursday1 meal
- Dinner
  Monday chicken — reheated with new sides
  ×4
Friday1 meal
- Dinner
  Pan-seared salmon, lemon-butter rice, asparagus
  Sleepover provisions in the order.
  ×2
Saturday1 meal
- Breakfast
  Pancakes and bacon for the sleepover crew
  Mia gluten-light: separate skillet, GF mix.
  ×6

The plan is not just “five dinners.” It is five dinners that fit this week, this household, this calendar.

What the layer knew

The household memory layer at work.

Aule knew Owen does not eat mushrooms because three weeks ago you said so once. Aule knew Mia is on the kindergarten gluten-light protocol. Aule knew you are trying to keep weekday cooking under thirty minutes. Aule knew the dishwasher repair window is Wednesday and that a loud kitchen would not work. Aule knew the salmon worked last month. None of this is set up in a form. The layer learned it from the household's actual life.

That is what the three-layer compounding memory does. The longer the relationship runs, the more the plan looks like something the household would have made itself, on its best week.

Scene three

The grocery order — and the approval gate.

$182 from Kroger, ready Sunday at 4pm. The layer chose Kroger because the household orders there most often and because the substitutions on the GF pancake mix were cleanest there. The order is built; the layer presents it for confirmation.

The approval gate kicks in. Grocery orders are inside the approval envelope by default. The household sees the order, the price, the delivery window, the substitution rules. One tap to approve. The order ships.

This is the structural difference between Aule and a chatbot that says it ordered the groceries. The layer cannot claim it placed an order it did not place because the household saw the order before it shipped.

Scene four

The receipted close.

Sunday at 4:07pm: the order is delivered. The receipted close comes back through Aule - the final amount, the delivery time, the one item Kroger was out of (the brand of burrata; subbed for the comparable house brand, per the household's substitution rules), the photo of the doorstep drop-off. The loop is closed and visible.

Scene five

The week after.

The next Sunday, Aule asks: “the salmon worked - keep it in rotation?” The household answers yes. The memory updates. Three months later, salmon shows up about once a fortnight without anyone having to schedule it. That is the layer earning trust - the gate around grocery orders stays in place; the gates around “is the household's shape of a week” loosen.

Under the hood

What ships today.

The meal-and-grocery loop runs on three live grocery integrations: the Kroger Cart API for direct order placement at Kroger and the Kroger family of stores; the Instacart Dev Platform Recipe API for Instacart catalog delivery (covering most major US chains); and Whole Foods through Amazon Fresh. The layer chooses the right one based on the household's preferences, the items on the list, the cost difference, and the delivery window the calendar can absorb.

All three are live in production. Adding a fourth store in a region the household is in (a regional chain Aule does not yet support) is an operations request, not a product roadmap item.

Common questions

Honest answers.

01Which grocery service does Aule use?

Whichever fits the household and the order. We have live integrations with Kroger (via the Kroger Cart API), Instacart (via the Dev Platform Recipe API), and Whole Foods through Amazon Fresh. The layer picks the right one based on the household's preferences, the items on the list, the cost difference, and the delivery window the calendar can absorb. If the household prefers a single store, the layer holds that preference.

02Does Aule charge the grocery order to my card directly?

The household holds the payment method; Aule presents the order for confirmation before the charge runs. Grocery orders are inside the approval-gate envelope by default - the layer never silently places a grocery order. Once you have run the loop enough times that you trust the layer, the per-household approval configuration lets you loosen the gate (e.g., auto-place orders under a threshold). The default is to ask.

03What if I want a different meal mid-week?

Tell the layer. The plan is a starting point, not a contract. If Tuesday's tacos turned into Tuesday's grilled cheese because soccer ran long, the layer updates the rest of the week, adjusts the grocery list if the order has not yet been placed, and remembers that grilled-cheese-Tuesday is a thing that happens. The household memory layer absorbs that into the pattern.

04Can Aule handle allergies and dietary restrictions?

Yes. Allergies and dietary patterns are part of the household memory layer from the onboarding call. The layer holds them by household member - one kid on a gluten-light protocol, another with a nut allergy, an adult cutting back on red meat - and applies them automatically to every meal plan. The household does not have to re-state them every week.

05What happens if an item is out of stock?

The grocery integrations return substitutions at order time. The layer applies the household's substitution rules (held in memory: "any whole milk for whole milk; never sub Diet Coke for Coke") and notes the substitution in the receipted close. If the substitution is non-trivial, the layer surfaces it for confirmation before the order ships.

Two ways to keep going.

See your own number

Take the Mental Load Index.

A five-minute assessment of your household operating load.

Open the assessment →

More loops

See what else closes.

Service appointments, dinner reservations, summer camp, and (at public launch) travel. The full surface of the layer.

Products →

Continue with Aule