If it leaves the house, it waits for a yes.
The method tells AI what to do. The guardrails tell it when to stop. Three classic ideas do most of the work: poka-yoke (mistake-proofing), jidoka (a human stop) and a lite FMEA (what could go wrong, and what prevents it).
Drafts, not sends
Nothing sends, spends, books or deletes without my yes. The safe path is the default path, so being careful isn't the only thing standing between a draft and a mistake.
Stops and asks
When a specialist is unsure, it stops and the item goes in “Needs you.” It handles the normal case and stops at the edge case, instead of guessing.
Draft-and-hold, honestly
Specialists stay in their lanes and hand work back up through the communicator. I see a short summary with the drafts attached, tap yes / edit / no, and only then does anything go out. It's a little slower than full autopilot. That's the point — the tap is where my judgment lives.
What goes wrong
Bots stall. Syncs drop. So there's a reliability heartbeat three times a day that checks the team is actually alive, and the rule is fail loud: if something breaks, it tells me plainly instead of quietly pretending.
Four jobs, one yes.
What could go wrong, and what stops it.
CI tool · FMEA-liteFMEA (failure mode and effects analysis) asks, for each step: what could fail, how bad would it be, how likely is it, and what prevents it? The classic version scores 1–10 and multiplies. The lite version uses high, medium and low, which is plenty for a household.
| What could go wrong | Effect | Severity | Likelihood | Risk | Guardrail |
|---|---|---|---|---|---|
| Emmy drafts the wrong tone to a close friend | Hurt feelings | High | Med | High | Family and close friends get extra care; nothing sends without my yes (poka-yoke) |
| Penny misses a bill reminder | A payment slips off the plan, stress | High | Low | Med | Bill senders route to Penny; a red tile three days out |
| Scout books the wrong dates | Plans broken, money spent | High | Low | Med | Scout never books: options and a draft plan only; I book |
| A routine stalls quietly | A brief never arrives and I don't notice | Med | Med | Med | Heartbeat three times a day; fail loud |
| Concierge shares a private detail with a guest | Privacy and safety | High | Low | Med | Codes and private details stay out of drafts (“keep out”); drafts held for my yes |
| Memory sync drops a day | The system forgets context | Low | Med | Low | The heartbeat checks sync; gaps show up in the morning brief |
From my houseWhen a new bot joins the team, it gets a RACI row and a few lines here before it gets a single task.
Print the blank →The filter everything passes through.
Your list will be different. These are mine, in my words.
Feed it so it learns you
Share context, preferences, the human stuff. The stack only gets sharp if you feed it — living context, not cold documentation.
Love as the filter
Presence over busy. If it crowds the people we love, it doesn't ship.
Have a communicator
One chief-of-staff voice that routes, briefs and talks human, so specialists don't scatter noise.
Make it visual
Dashboards, the team map, week-at-a-glance. Don't bury the system in text-only tools.
Frictionless
Lowest-friction capture wins. Voice beats typing; a wearable; ambient taps someday.
Sundays for being present
Away from screens and tech. More present time is the whole point of the system.
A thoughtful partner
Not a guilt machine. Fail loud, coach in the moment.
Human voice, always
Especially with guests and people we love. Never canned.
Quiet backends
Memory lives in the archive and the vault. Chat and the visual home are the only things that push.
Cost-honest, lean
Tools earn their keep. Systems that stick — so the family has room.