01
Anticipating
The week shows up before the week shows up.
A child’s birthday is six weeks away; Aule surfaces the planning window before the calendar surfaces the day. School registrations are about to open; Aule is already on the page.
The domains
Capabilities,in receipts.
Examples of loops the household intelligence layer closes today. Scheduling, childcare, food, vendors, finances, travel — every domain on this page is the same kind of work, the operational weight underneath the home, closed end-to-end by the layer instead of one person’s head. What follows is the receipts version: not a brochure of features, but the actual things Aule produced for a household last Tuesday. The layer grows as we ship more.
Most households start by handing over two domains and move the rest in as comfort grows. No household onboards with everything running at once. New domains move in when you decide they should — Aule does not push you off a ledge.
The shape underneath
Every capability is the same five moves.
The domains are surface area. Underneath, the work is always the same five operating motions — applied to plumbers one minute and to birthdays the next.
02
Routing
Aule picks who or what should do the work.
Plumber needed: Aule selects from the household’s preferred-vendor list, requests three quotes, returns context — "in line with the last two repair quotes from this vendor" — and waits for your call.
03
Deciding within rules
You set the lines. Aule respects them, every time.
New vendors above a spend threshold ask first. Recurring workflows the household has approved once execute automatically. Anything touching a child’s identity is escalated, always.
04
Closing loops
The plumber came. The refund posted. The form was sent.
Most household to-dos linger because nobody circled back. Aule follows up until a loop is closed — closed loops are how cognitive surface area actually shrinks.
05
Learning the household
The names of the dog and the kids and the in-laws — saved once.
Over time, Aule accumulates household-specific knowledge: preferred vendors, food preferences, school routines. This knowledge stays inside your household’s instance — not pooled, not used to train shared models.
The domains
Each domain, with its receipts.
Each capability below is a domain where Aule closes loops end-to-end. The receipts are the actual outputs — the kind of line a household member sees in chat or in the morning brief.
01 · Scheduling
The family calendar held by an operations team.
Two-partner reconciliation, kid routing, vendor windows, recurring appointments that never get forgotten. Aule sits inside the calendar instead of next to it — proposing, holding, reshuffling — so the calendar stops being one person’s second job.
- 01Eleven weeks of summer placed by kid, with deposits queued for your nod.
- 02Doctor reschedules itself when the soccer schedule moves.
- 03The dentist surfaces eight days out, not the morning of.
Capability detail page coming with Wave 2.
02 · Childcare
Sitters, school logistics, the pediatrician cadence — held.
Camp registrations open before you remember they exist; the registration is in your inbox with a draft of your card. Allergies, medication, drop-off routines, the names of the friends and the friends’ parents — saved once, surfaced when relevant.
- 01Camp registrations submitted in the first window. No more "they filled up in three minutes."
- 02Pediatrician follow-ups closed instead of forgotten.
- 03Sitter briefed in your voice, every time, with the things you would have remembered to mention.
Capability detail page coming with Wave 2.
03 · Food
A week of dinners that already know the household.
A week of meals planned around the household, allergies respected, leftovers used on purpose. Grocery list routed to whichever store actually carries what your family eats — and delivered to the window you said you wanted.
- 01Six dinners on the table by Sunday night, with a grocery list to match.
- 02Mia’s gluten-free swap noted on the days it matters.
- 03Tuesday’s slow-cooker started at 7:30 a.m. when the morning was already loud.
Capability detail page coming with Wave 2.
04 · Vendors
Three vetted quotes, booked, paid, followed-up.
Plumbers, cleaners, lawn, repair, contractors — every loop closed. Three quotes pulled with your home address and recent history, the recommended one called out in context, and the post-visit follow-up sent before you have time to remember it should have been sent.
- 01Three plumbers for the kitchen-sink leak, the mid-quote booked, the loop closed after the visit.
- 02HVAC maintenance scheduled before the season the system always fails in.
- 03A photo of the leak attached to the quote request — context the household used to have to carry.
Capability detail page coming with Wave 2.
05 · Finances
Recurring charges audited weekly, in plain English.
Subscriptions flagged. Anomalous spending reviewed in language a tired parent can read at 9:47 p.m. Bill-pay coordinated, not just tracked. Spend guardrails the household sets at onboarding — anything above them is a hard stop, not an auto-charge.
- 01Two duplicate streaming subscriptions surfaced for cancellation. Saved $22.99/mo without a "let me look into it later."
- 02$480 plumber charge from March matched to the quote and cleared.
- 03Groceries trending $312 under budget, with the surplus rolled into June’s travel category unless you redirect.
Capability detail page coming with Wave 2.
06 · Travel
Flights, hotels, ground transit, packing — all rendered.
Three packing lists generated by kid and by weather, awaiting your nod. Dog sitter confirmed, key in the lockbox. Mid-trip changes handled without a group-text war — the seat you actually wanted on the rebooked flight is the one the agent took.
- 01Aspen, March 14–21: flights, lift tickets, ski-school waitlist, dog sitter, packing lists — held.
- 02Cancellation refund posted automatically when the storm rolled in.
- 03Itinerary handed to grandma in a format she will actually read.
Capability detail page coming with Wave 2.
Memory, in three layers
A household has a memory. Yours just is not written down.
Every capability runs on top of three layers of memory — facts, patterns, decisions. You and Aule keep them current as life changes: a new vendor, a new allergy, a kid who outgrows a camp.
Layer one
Who is in the house.
Members, ages, schools, vehicles, pets. Vendors you trust, banks, doctors, sitters. Allergies, diets, the thing your kid will not eat. Facts that do not change daily — edited by you, read by Aule.
Layer two
How you actually live.
Liam has soccer most Saturdays. You skip cardio Mondays. The HVAC guy is Frank, not Joe. Birthdays you mark and birthdays you do not. Learned over weeks, refined by your approvals.
Layer three
Every action, on the record.
What was done. What was proposed. What you said yes to. Why this plumber and not that one. A receipts ledger, not a black box — audit a Tuesday in November and see why dinner was salmon.
The line you draw
Full auto by default. Two beats of confirmation.
Every capability runs against the same approval gates. Aule closes the loop end-to-end unless one of the two default gates trips — and the layer gradually loosens those gates as it earns your trust.
Default
Auto.
Closes the loop end-to-end. Vendor visits under the spend gate, dinner reservations, recurring renewals inside the rules, subscription verifications. Receipt lands in the morning brief.
Gate 01
Confirm groceries.
Any grocery order, any size, asks first. Graduates after ~30 days and ≥4 successful confirmations to "approve the meal plan, run orders against it."
Gate 02
Confirm spend ≥ $200.
Any single spend at or above $200 surfaces with the quote and the context. The household can raise the threshold, lower it, or remove it as the layer earns the latitude.
Full policy at /products/trust-and-safety.
The questions we hear most
Capabilities FAQ.
01Are these the whole list, or examples?
Examples. The household intelligence layer is open-ended by design — anything that fits the shape of "a household decision someone usually has to make and then chase down" can move under it. New capabilities ship as patterns stabilize across the founding cohort. The layer grows as we ship more.
02Can I turn a capability on without turning the others on?
Yes. Households start by handing over one or two domains — usually scheduling and food, or vendors and finances. The rest move in as you choose to hand them over. No household onboards with everything running at once.
03Is "vendor coordination" actually Aule on the phone, or just an email to me?
It is Aule sourcing the vendors, requesting the quotes, drafting the replies, scheduling the visit, and following up after. Anything that requires a real-money authorization waits on you. Anything that does not — the back-and-forth, the rescheduling — Aule holds.
04How does Aule know what my household actually eats?
You tell it once, in the onboarding interview. Then it watches the receipts: what came back from groceries, what got eaten, what got tossed. The week-two meal plan is closer to your house than the week-one plan — that gap closes fast.
05What does "closed loop" actually mean for me on a Tuesday?
It means the plumber visit ends with a follow-up confirming the leak is fixed and the warranty is on file. The refund posted gets verified against the receipt. The form Aule submitted at the school is confirmed received. Most household to-dos do not fail at the doing — they fail at the closing. Aule closes them.
The next step
See your household’s mental load in five minutes.
The Mental Load Index is a five-minute assessment that scores your household across thirty cognitive-labor domains. The number is the start of the conversation.