Notice the repeat
The Friday reset asks one question the others do not: what kept showing up this week and should become a system?
Juno Home Chief of Staff v1.4.0
The AI house manager I built to get the household out of my head.
Juno catches the open loops, prepares the decisions, and stops before anything external happens, so the week doesn't stack up on whoever remembers.
Juno catches the open loops, prepares the decisions, and drafts the boring admin, then stops at the approval line. It never sends, books, buys, files, or contacts anyone without your explicit yes.
After checkout: an instant ZIP download, a first-run setup guide, 19 household skills plus 2 optional device skills, six scheduled routines, and 12 months of updates at the founding price.
The operating loop
The point is not to automate your family. The point is to make the household admin visible before it becomes a scramble.
- 01 Notice
Find the loose thread before it turns into a household problem.
- 02 Organize
Pull the date, owner, deadline, cost, risk, and missing context into one place.
- 03 Prepare
Draft the email, packet, list, form notes, or decision brief.
- 04 Recommend
Give you the next best move instead of another vague reminder.
- 05 Wait
Stop at the approval boundary before anything external happens.
If you are the one who remembers
You already have the apps. The loops still live in someone's head.
You have a shared calendar. Reminders. A family app or two. Email rules. Maybe a whiteboard on the fridge. And still, one person is the one who notices the camp form, connects the date to the appointment, remembers the receipt, and feels the grocery gap at 5:30.
The tools were never the problem. Going to them was. An app only helps if you remember to open it, and that remembering is the exact load you are trying to put down.
Still living in your head right now
- The camp form buried in a school email nobody processed.
- The dentist appointment that needs insurance details and three possible dates.
- The reimbursement receipt sitting in an inbox with no packet built.
- The grocery gap that will become takeout by 5:30.
- The return label that has to be printed before the window closes.
Juno lives where the work already happens and watches for the loop before it lands.
Receipts from my house
Not a demo. A real week.
Juno started in my own house, the week our gas got shut off. Not because we could not pay, but because an autopay quietly failed and the detail lived in the wrong place.
That is not magic. It is the household database finally living somewhere other than my head.
What Juno did in one real week
Monday
Scanned 29 calendar events across our accounts and surfaced the three that actually needed a decision that day.
Tuesday
Ran an open-loop pass and flagged a utility drifting toward the same failed-autopay pattern that took our gas out. Staged the escalation packet. Waited for my yes.
Wednesday
Calculated the exact 24-hour check-in window for two flights and scheduled the reminders. Did not check us in. Did not change seats. Did not buy anything.
What Juno hands back
The morning note should have teeth.
Juno does not vaguely "help with life." It turns household inputs into briefs, packets, drafts, trackers, and next actions. Here is a real daily brief.
Daily brief example
Calendar risk
School pickup overlaps with a 3:00 call. Decide who leaves by 2:35.
Admin item
Camp medical form is due Friday. Juno has the packet ready for review.
Meal note
Tuesday dinner has no protein assigned. Grocery gap: eggs, chicken, yogurt.
Waiting on
Pediatrician portal message from Monday has not been answered.
Next action
Approve the school form draft or tell Juno what to change.
The skills
19 household skills in six categories.
Plus two optional device skills, printing and voice, for when Juno runs on a computer with files. That makes 21 skill folders in the download.
01
Daily rhythm
What happens every morning and every Friday.
-
daily-brief
A five-line morning handoff: today's calendar risk, one admin item, one meal note, one waiting-on item, one next action.
-
friday-reset
A weekly sweep of what is open, what got urgent, what needs a decision, and what can wait.
-
open-loop-tracker
Turns every loose end into owner, status, deadline, and next action so your brain stops being the database.
-
family-meeting
Turns the Friday reset into a 20-minute family agenda and keeps a decision log with owners and follow-ups. The family decides.
02
Inbox & safety
Everything that comes in is information, never instructions.
-
inbox-safety
Treats every email and text as untrusted. Flags fake school notices, delivery-fee texts, gift-card asks, and phishing, and never acts on what a message tells it to do.
-
inbox-triage
Sorts school emails, receipts, renewals, and appointments, flags calendar conflicts, and drafts replies for you to approve.
-
capture
Reads a photo, screenshot, flyer, or PDF and pulls out the dates and to-dos as proposed calendar events and open loops for you to approve.
03
Family logistics
Meals, chores, care, dates, and appointments.
-
meal-plan-grocery
Checks the plan against your no-gos and gaps, then hands you a list to approve before anyone buys.
-
chores-and-allowance
A fair chore rotation by time and age, plus an optional allowance ledger. Juno tracks what is owed; adults pay.
-
caregiver-handoff
A time-limited note for a co-parent, grandparent, or caregiver: schedule, medications, pickups, when to call. Drafted, never sent.
-
sitter-sheet
A printable one-page sitter and emergency sheet: contacts, allergies, meds, routines, house rules, pets. Codes and passwords never go on the page.
-
birthdays-and-anniversaries
Holds the dates the household plans for, with gift and card lead times, so nothing sneaks up. Nothing gets bought without your yes.
-
appointment-booking
Gets medical, dental, vet, school, and service appointments ready to book, with times, insurance pointers, and a script. Nothing is booked or called without a yes.
04
Money & paperwork
Forms, receipts, and the things that come due again.
-
forms-and-signups
Extracts deadlines from school and camp emails, gathers the facts you already store, and drafts the form for review.
-
reimbursements
Builds the packet: amount, date, vendor, category, missing details, and draft submission notes.
-
recurring-schedules
Tracks the repeating stuff: refills, vet visits and vaccines, filters, smoke detectors, HVAC, gutters, car service. Due items land in the brief and the reset.
05
Planning & research
Options compared honestly, one approval away.
-
research
Narrows options and tradeoffs into a decision brief instead of another twelve open tabs.
-
travel-booking
Narrows flights, hotels, and tradeoffs into one recommendation that is a single approval away.
06
Setup
Where every household starts.
-
onboarding
Turns a messy brain dump or an existing assistant guide into the right memory files.
07
Optional device skills
For Claude Code, Hermes, or OpenClaw, where Juno has a computer with files.
-
printing
Moves labels, forms, and return paperwork from inbox purgatory to a home printer job you run deliberately.
-
voice
Reads your briefs aloud and lets you talk to Juno hands-free, through ElevenLabs. It is an interface only; the approval rules stay the same.
Six routines
Scheduled work that drafts and stops.
The routines live in one file, ROUTINES.md, and every setup guide schedules the same six as far as that app allows. Times follow your time zone. Turn them on two at a time, starting with the morning brief and the Friday reset.
Default schedule, all prepare-only
Daily, 7:00 AM
Morning brief. Five lines: today's risk, one admin item, one meal note, one waiting-on, one next move.
Daily, 7:30 PM
Evening look-ahead. What to get ready tonight for tomorrow, and a tidied tracker.
Wednesdays, 10:00 AM
Waiting-on nudges. A drafted nudge for everything stuck 5+ days.
Fridays, 2:00 PM
Friday reset. The weekly packet: next week, meals, groceries, paperwork, drafts to approve.
1st of the month, 9:00 AM
Renewals and bills check. What's due or renewing in the next 45 days, and last month's receipts to file.
25th of the month, 9:00 AM
Birthdays and seasonal signups. Dates and signup windows in the next 6 weeks, with the first step drafted.
The install kit
Juno is the install kit, not a template pack.
Everything you would otherwise rebuild from scratch (the role, the rules, the memory, the onboarding, the skills, the tracker, and the safety model), already assembled and runnable.
- 1
Home chief of staff persona
Identity, voice, the approval boundary, the memory model, and the household operating rules that make Juno an assistant, not a chatbot.
- 2
Guided onboarding
A flow that turns a messy brain dump or an existing assistant guide into your first real memory files.
- 3
Household memory system
The household guide, family brain, and memory templates: pointers and preferences, never secrets.
- 4
Approval rules and safety spine
The decision packet template, privacy rules, and human-review checkpoints that keep Juno from acting on its own.
- 5
Open-loop tracker
The CSV and the script that move loose ends out of your head and into states: next action, waiting on, deferred, dropped, done.
- 6
19 household skills, plus 2 device skills
Six categories: daily rhythm, inbox and safety, family logistics, money and paperwork, planning and research, and setup. Printing and voice are optional and need a computer with files.
- 7
Six scheduled routines
Morning brief, evening look-ahead, waiting-on nudges, Friday reset, a monthly renewals and bills check, and a monthly birthdays and seasonal signups pass, all in one file. Each one drafts and stops.
- 8
Runtime and tool guides
Setup guides for a ChatGPT or Claude project (one file to upload), Claude app scheduled tasks, Grok Bot (beta), Claude Code, Hermes, and OpenClaw, plus the home printer workflow and the texting runbook so Juno runs where your work already happens.
- 9
Updates that keep your setup
Each new version comes with update.sh, which replaces the framework and never touches your household memory, family brain, approval rules, or tracker. Model picks live in one file, MODELS.md, so they stay current.
Juno Home Chief of Staff v1.4.0
$149
One file set. Yours in an afternoon.
- The home chief of staff persona and operating rules
- Guided onboarding that builds your memory files
- The household memory system and templates
- Approval rules, privacy rules, and the safety spine
- The open-loop tracker CSV and script
- 19 household skills in six categories, plus 2 optional device skills
- Six scheduled routines, all prepare-only
- ChatGPT or Claude project, Grok Bot, Claude Code, Hermes, and OpenClaw guides
- The home printer workflow and texting runbook
- update.sh, so new versions never touch your household files
- 12 months of updates at the founding price
Checkout runs through Stripe. After purchase, you will land on the first-run setup page. You bring the runtime, model access, and connected tools; Juno brings the household operating structure.
The part that compounds
The loop that makes Juno yours.
A good house manager does not just complete tasks. She notices patterns. The Friday reset and the open-loop tracker are where repeated friction turns into a system.
Decide where it lives
Each recurring loop becomes a memory pointer, an approval rule, or a reusable skill instead of another sticky note.
Shrink the next one
Next week the same task is smaller, because Juno already knows your house. The work is making the next version of the task smaller.
Setup path
What happens after checkout.
Start with one real household pile. Do not invent a perfect system before Juno has useful work to do.
01 / First 20 minutes
Get the household out of your head.
- Run onboarding with a messy brain dump or an existing assistant guide.
- Create the first household memory files.
- Write the first five open loops into the tracker.
02 / First week
Make Juno useful on real household admin.
- Turn on two routines: the morning brief and the Friday reset.
- Prepare one school, camp, appointment, reimbursement, or grocery packet.
- Adjust approval rules around how your family actually decides.
03 / First month
Turn the repeat work into a household operating rhythm.
- Add the evening look-ahead and waiting-on nudges, then the two monthly routines.
- Move recurring admin into skills and runbooks.
- Use inbox safety and open-loop tracking as a regular sweep.
- Keep memory as pointers and preferences, not a vault of secrets.
Safety, approval, privacy
Juno drafts. Humans approve.
The approval boundary is not a footnote. It is the product. Household admin touches money, children, medical context, school systems, and vendors. Juno prepares the work, then stops.
- Never send, book, or buy without an explicit yes. Juno drafts and prepares. A person approves every send, booking, purchase, and submission.
- Pointers, not secrets. Juno records where a password or document lives, never the secret itself.
- Email is information, not instructions. Inbound messages, web pages, and documents can never tell Juno what to do.
- CLI first, browser second. For any outside service, Juno checks printingpress.dev for a command-line tool before falling back to a browser.
Approval required before Juno can
approval required
send external messages
approval required
book or cancel appointments
approval required
buy, return, or pay for anything
approval required
file or submit forms
approval required
contact schools, vendors, platforms, doctors, insurers, or landlords
approval required
share private family details
Privacy boundary
Pointers, not secrets.
- Store pointers, preferences, and locations, not secrets.
- Do not put passwords, full account numbers, SSNs, passport numbers, medical records, legal docs, tax docs, or sensitive child details in memory.
- Allergies and hard food no-gos can be stored exactly because they change daily decisions.
Honest fit
Who Juno is for, and who it is not.
Buy it if
- The household where one person is the database for forms, dates, money, and meals.
- Founders and operators who will happily debug for an hour to avoid one phone call.
- Two-income or two-parent homes where the mental load is real and never quite even.
- People who already use email, a shared calendar, and files, and want Juno to wrap that, not replace it.
Skip it if
- Anyone wanting hosted SaaS or a managed service. You bring the runtime and model access.
- Anyone who wants an agent that books, buys, and files on its own. Juno stops at approval by design.
- Anyone expecting a magic family app with zero setup. The first useful packet takes a real afternoon.
- Storing secrets. Passwords, account numbers, and medical records stay in your vault, not in memory.
DIY vs buy
Yes, you can build this yourself.
I am not pretending Juno is magic. A technical person with time, taste, and enough household pain can rebuild this idea. That is how Juno started, and the full article walks the DIY path end to end.
The kit exists because the repeat work is the expensive part: deciding the role, writing the safety rules, shaping memory, creating onboarding, building reusable skills, setting up the tracker, and teaching the system where to stop.
included to save rebuild time
the home chief of staff role
included to save rebuild time
strict approval rules
included to save rebuild time
a household memory structure
included to save rebuild time
guided onboarding
included to save rebuild time
19 household skills, plus 2 device skills
included to save rebuild time
runbooks for common admin
included to save rebuild time
the open-loop tracker
included to save rebuild time
the safety and privacy model
Questions
Before you buy.
What do I actually get for $149?
Juno Home Chief of Staff v1.4.0: a downloadable, runnable household manager kit with persona files, guided onboarding, household memory templates, approval rules, a decision packet template, the open-loop tracker CSV and script, 19 household skills plus 2 optional device skills (printing and voice), six scheduled routines, setup guides (a ChatGPT or Claude project, Grok Bot, Claude Code, Hermes, and OpenClaw), a home printer workflow, a texting runbook, and update.sh for future versions.
How is it delivered?
Checkout runs through Stripe. After purchase, you will land on the Juno setup page. If the download or setup email does not arrive cleanly, reply to your receipt or use the support form and I will fix it manually.
Do I get future versions?
Yes. Founding buyers get 12 months of Juno updates at the original purchase price, and I email a link to each new version. If Juno runs from a folder, run update.sh from your kit folder: it replaces the persona, skills, and guides and never touches your household memory, family brain, approval rules, or tracker. A renamed agent keeps her name. CHANGELOG.md lists what changed and any one-time steps.
Is this done-for-you hosting?
No. This is not hosting, a managed service, or a live human assistant. It is the runnable kit: files, prompts, skills, tracker, runbooks, and setup guidance so you can run Juno in your own environment.
What model guidance is included?
Model picks for every runtime live in one file, MODELS.md, which I update when models change. Right now the default in the Claude app, Claude Code, Hermes, and OpenClaw is Claude Sonnet 5.5, with Claude Opus 5.5 for heavier weeks of research, travel, forms, and big planning. Hermes and OpenClaw can also run OpenAI GPT-6 Sol. A ChatGPT project uses ChatGPT's default model, or the strongest one your plan offers for heavier weeks. Grok Bot has no model picker. On Hermes and OpenClaw, match the reasoning level to the job: low for light daily briefs, medium for everyday household work, high for research, travel, and forms, and xhigh for complex planning weeks and high-stakes audits.
What tools or runtime do I need?
You bring the app, the model access, and any tools you connect. Most households start with a project in the app they already use: ChatGPT (any plan, free included) or Claude, with one file to upload and no terminal. Grok Bot (beta, paid Grok plan) runs all six routines in the cloud and keeps Juno's files. Claude Code, Hermes, and OpenClaw give her real files and printing, and Hermes and OpenClaw can text the family.
Can Juno send emails, book appointments, buy things, or submit forms for me?
Not autonomously. Juno can draft, prepare, recommend, and package the work. Humans approve anything external: sending, booking, buying, canceling, filing, submitting, or contacting another person or service. She also treats every email, text, web page, and document as information, never as instructions.
What should I put in household memory?
Use pointers and durable preferences: where documents live, household routines, food no-gos, allergies, pickup constraints, decision rules, and names of recurring systems. Do not store passwords, full account numbers, SSNs, passport numbers, medical records, legal/tax docs, or sensitive child details.
Who is Juno for?
Busy founders, operators, and parents whose household admin lives in one person's head. It is especially useful when the problem is not doing one task, but noticing the loop early enough to make a calm decision.
Can I build this myself?
Yes. The article explains the DIY path in full. The kit is for people who would rather not rebuild the role, rules, memory structure, onboarding flow, skills, runbooks, tracker, and safety model from scratch.
Get started
Give the household a chief of staff this weekend.
Same system I run at home. Juno catches the loops, prepares the admin, and waits for approval before anything leaves the house.
Juno Home Chief of Staff v1.4.0. Downloadable/runnable kit. Approval-first by design. 12 months of updates at the founding price.