Hermes family OS · 1 of 6 · what you get
A Tuesday, on a timeline
The finished stack is invisible most of the day. This is what it looks like when you make it visible.
Below is the mock this whole plan builds toward: one household’s day, every agent action on one timeline, each event tagged with which profile acted and on which surface. The family is invented — Priya (household lead), Dele, Sam (15, they/them), Mira (8) — but every event maps to a real mechanism, itemised under the mock. Static data; the aesthetic is deliberately “dashboard on the kitchen wall”.
-
07:10
Morning brief lands in the family group
Weather, each member’s calendar, bin day.
Sam — mouthguard, hockey after school. Recycling goes out tonight.
profile: householdtelegram · family groupcron 07:00 -
07:11
School-run clash caught
Calendar shows Dele’s 08:30 stand-up against Mira’s 08:25 drop-off.
Priya, can you take the run? Dele’s stand-up moved to 08:30.
Priya 👍 — the brief updates, nothing is rebooked without a human.profile: householdtelegram · family groupcalendar via MCP -
12:40
Sam DMs their own agent
add oat milk and those seaweed things
— logged to the shared grocery list. Sam’s agent has no house credentials and its own memory; the DM stays between Sam and it.profile: sam-agenttelegram · DMvault: groceries.md -
16:00
Grocery list consolidated
The week’s group-chat mentions plus member adds, deduplicated and sorted by aisle; pushed to the shared Notion page.
23 items. Nothing flagged — say ‘checkout’ and I’ll load the cart for review.
profile: householdtelegram · family groupcron 16:00 · notion via MCP -
17:25
House warms up before anyone’s home
Calendar says hockey ends 17:15; heating to 20 °C, hallway lights on at dusk. One service call, no announcement — the group only hears about exceptions.
profile: householdhome assistantha_call_service -
19:05
Mira asks the group for movie night
can we have the film lights
— living-room scene set. Third Friday-ish request this month, so the agent offers to make it a one-word skill:Want /movienight?
profile: householdtelegram · family groupha_call_service · skill offer -
21:30
Day closes, quietly
Tomorrow’s first event, one line:
Cart’s loaded for Thursday delivery — Priya to review and pay.
Then silence until 07:00. The agent never pays.profile: householdtelegram · family groupcron 21:30
What’s real, what you wire, what you build
- Real, built in: the messaging gateway with Telegram/WhatsApp
group chats, DM pairing, the cron scheduler (natural-language jobs, delivery to
any platform), profiles, skills, and the Home Assistant tools
(
ha_call_serviceand friends). - You wire: the calendar. Hermes has no built-in calendar — the 07:11 clash-catch works because the household profile has a calendar MCP server connected (a Google Calendar MCP server is the usual class of solution) and the cron prompt says “read the calendar before you speak”. Same for the Notion push: a Notion MCP server.
- You build: the shared grocery list and the “vault” it lives in. That’s a directory plus a skill that maintains it — not a Hermes feature. Details and the honest limits (per-member memory in groups is not built in either) are on the architecture page.
- Deliberately absent: autonomous checkout. The cart gets loaded (cloud browser, metered, fragile — trap № 6); a human presses pay, forever.
This mock is also the plan’s feedback artifact: the last prompt stage shares this page with your actual household so each member can pin objections on it — “don’t message me before 9” is cheaper to learn now than after pairing.