The Daily Rhythm
Step 7 · The Job
A job description with no rhythm produces an agent that works only when poked. This page is the schedule mine runs to, written out so you can see the shape.
The specifics will differ for your household. The shape is what to copy.
The schedule
Section titled “The schedule”| Time | What runs | Why then |
|---|---|---|
| 03:00 | A snapshot of the system’s own state | Cheap at night, and it is the record of what changed |
| 05:00 | The morning brief, by email | It is waiting before I sit down |
| 06:00, 14:00, 22:00 | Reconcile the shopping list with the household’s own lists | Three passes so any device can be the one that is right |
| 07:00 | Check the family calendar for clashes | Problems are cheapest to fix before the day starts |
| 07:00, then every 2 days | Watch fares on a route I fly, and email only if worth acting on | Watching is cheap; alerting is not |
| Every 30 minutes, 07:00–22:00 | Check its own mailbox | This is where the household’s paperwork lands |
| Every 2 hours, 08:00–22:00 | Process anything forwarded to it | Only what I choose to forward gets handled |
| 08:00 and 20:00 | Watchdog: did every scheduled job run? | Silent failure is the failure that hurts |
| 09:00 | Reorder checks — the things I buy on a cycle | Before I run out, not after |
| 10:00 | The morning sweep | Reads everything overnight, acts on what it can, escalates the rest |
| Hourly, at :12 | The continuous watch | Notices the unusual across all of it |
| 18:00, Sunday–Friday | The school digest | Assembled the evening before a school day, by email |
| 20:30 | The evening sweep | Tomorrow checked, and flagged tonight |
| 20:30, Sundays | The weekly review | What moved, what stalled, what is next |
| 21:00, twice a week | It asks me one question about the household | How the context deepens without an interview |
| 22:00 | Back up its own state, and tidy its written notes | Nobody is waiting |
| Every 15 minutes | Watch a download queue | Short-lived, and only matters while it is running |
| Every 2 hours | A security check on its own scheduled jobs | The thing that checks the checks |
| Weekly | Audit its own setup, and whether the pages describing it are still true | This is the loop that keeps documentation honest |
The three rules that keep this from becoming noise
Section titled “The three rules that keep this from becoming noise”A quiet run stays quiet. If a scheduled job finds nothing, it says nothing. This single rule is the difference between an assistant people like and one they mute.
Alert on change, not on state. “The parcel is in transit” is not news. “The parcel was delivered” is. The agent compares against what it already knew and speaks only when that changed.
One message, not five. Related findings consolidate. Three notifications about one situation is three times the interruption for the same information.
Watching versus nagging
Section titled “Watching versus nagging”The most valuable scheduled work is watching things in flight — deliveries, bookings, forms, fares. Getting this right took the longest of anything in this build.
| Good watching | Nagging |
|---|---|
| Alerts when a parcel is delivered | Alerts every day that a parcel exists |
| Flags a booking that changed | Repeats the booking daily, unchanged |
| Warns once about a form due soon | Reminds every morning until it is done |
| Mentions an unusual door event | Narrates every door |
The pattern: speak on transition. Something moved from one state to another and I might want to know. Everything else is noise.
My test before adding a scheduled job: what would this household miss if it never ran? If the honest answer is “nothing”, the job does not get created.
Why silence is the design
Section titled “Why silence is the design”An over-eager agent does not get fixed by an instruction. It gets muted — and then the household stops reading anything it sends, including the one message that mattered.
That is why I treat silence as a feature. This page is mostly a list of things that do not happen.
Where to start
Section titled “Where to start”- One digest, once a day. The single highest-value scheduled job.
- One watcher, on something reversible. Deliveries are ideal.
- Add the watchdogs and backups last. They are boring and essential, and they will hide a problem in the first two if you add them too early.
A Day in the Life — the same schedule, seen from the inside.