Most home software starts in the wrong place. It wants to assign chores, track habits, and produce a dashboard. The house slowly acquires another surface to maintain, which is an impressive solution to the problem of already having too much to maintain.
The real bottleneck in a home is usually mental overhead.
Dinner. Library books. Tomorrow’s appointment. The cup the toddler can reach. The tape that used to be in the drawer before the cardboard-elevator project. The shoes that only matter on Sunday morning. If one parent carries all of that in live memory, the house only works until that parent gets tired.
The useful family agent probably starts smaller than most people imagine. Not a weirdly anthropomorphic robot in the kitchen – a text reminder to put out the church shoes on Saturday night. That’s not glamorous, which is exactly the point. Glamour is how you end up with a dashboard nobody opens.
The analog version already existed
Cheryl Mendelson’s Home Comforts is almost 900 pages of household state made visible. It covers bedding, stains, food safety, fabric care, dust, china, fire, law, closets, and the unglamorous mechanics of keeping a home livable. OpenLibrary’s back-cover summary lists things like folding fitted sheets, reading care labels, keeping surfaces free of food pathogens, and making a bed with hospital corners.
That’s not lifestyle content. It’s a maintenance manual for the machine everyone lives inside.
A good household reference book doesn’t do the laundry for you. It makes the why and the how legible enough that someone else can learn them. That’s the part most family tech misses. The goal is to stop making one parent the database, not to automate the parent out of the home.
A house is a context problem
Parents are constantly deciding what belongs in view:
- What matters today?
- What can wait?
- What does the child need to reach without asking?
- What needs to be remembered next time?
- What should not become a permanent rule?
This is why a household board is more interesting than a chore chart. A chore chart says who has to do what; a household board says what the house currently knows. Dinner. Homeschool block. Library day. Grandparents visiting. Packing list. Church shoes. The thing that always gets remembered ten minutes too late.
Once that state is visible, people can act on it without querying the parent who happens to be carrying the whole room in her head.
A useful family agent forgets on purpose
A family agent that remembers everything isn’t helpful. It’s a surveillance scrapbook.
The household board works precisely because the parent edits it. Wednesday’s reminder is gone by Thursday. The Sunday-shoes rule stays until the kid outgrows the shoes. Most of what runs a house is a small set of facts that expire on a schedule the parent quietly knows.
The machine has to know the same things, with the same shelf life:
- Who added this, and when?
- Does it still apply next week?
- What would make it false?
- Should it be visible to everyone, or just to the parent?
“He likes airplanes” is useful until it goes stale. “Pack church shoes on Saturday night” is useful until the routine changes. “He melted down after a late snack” might be a pattern, or it might be Tuesday. The machine shouldn’t convert ordinary childhood into a permanent profile.
Multi-agent only matters when the boundaries are real
This is where multi-agent systems get less silly.
Most agent demos split roles because org charts are easy to draw. Planner agent. Researcher agent. Writer agent. Manager agent. Congratulations, the bureaucracy has learned JavaScript.
The useful split is boundary design, not roleplay. One agent to handle household memory, one for calendars, one for meal planning, one for homeschool notes – and they don’t all need the same tools, the same data, or the same retention rules. The meal agent doesn’t need private homeschool observations. The homeschool agent doesn’t need purchasing history. The calendar agent has no business rewriting your business website. The boundary is the safety mechanism.
What I would actually build for home
Start with a wall-mounted daily view:
- Dinner
- Homeschool plan
- Appointments
- Library books
- Delivery windows
- Tomorrow after 5:30
- The one thing we forget every time
Then add memory, carefully. Not “remember everything about the family.” Remember recurring situational needs. Remember where the system got them. Let the parent edit them, let the parent delete them, and surface the right ones at the right time.
A Saturday-evening rule with useful context might look like this:
Source: parent added after two Sunday-morning shoe searches. Condition: Saturday after dinner. Surface: wall display and parent phone. Text: “Put church shoes by the door.” Delete: one tap, once the reminder becomes routine.
That’s the family AI I want. Not another place to check. Not a chatbot in a chore-chart costume. A home surface that stops making the parent the only API.
The agent can hold the state. It can’t do the building. For the part where you and your kid actually make something together, I wrote a twelve-week project curriculum – hands-on activities for ages 2-6, designed to run in the margins of a normal week. No coding required.