← the lab · the atelier

Sheet 40 · agent systems

How I run my life

Can I hand the planning and follow-up in my life to a system, and tell whether it actually helps? One orchestrator writes, memory comes in four kinds, every captured item needs a verbatim quote, a nightly job runs the planner in shadow mode, and a draft rubric tracks the effect over time.

Question

Can I hand the planning and follow-up in my life to a system, and tell whether it actually helps?

I think AI should take our busywork. It should make what we can already do far more efficient and leave us the thinking part. When I applied that to my own life, I started by tracking and checking the most basic things, and I add the next layer only once that level is in order.

The system runs on Hermes Agent, an open-source agent runtime.

Architecture

1Interfacesafter every turn a fastmodel proposes the openitems it heard, eachwith a quote; codedrops any quote not inthe turn2Orchestratorchecks what comes inMemory, workers,stores3MEMORY4WORKERS5STORES6Routines13 scheduled jobs7Auditchecks on the systemitselfDesktop appWindows PC and MacTelegramon my phoneVoice modeOne agenton a large hosted model; the only part that writesAlways-on notesa short notefile and aprofile, inevery turnFact store19 facts,searched whenneededSkills120 files forrecurring workNotes vaultthe long-termrecord; ActiveThreads openseach sessionWorker agentsin parallel,each with aclean contextKanban boardmulti-step workSession ledgerinbox: toTodoist ordroppedTodoistthe one tasklistNight planner06:00; proposes,writes nothing yetReviews,reminders,watchers, digestsand a buildmonitorSunday reviewthis week againstthe lastQuote checkPlanner validatorSession-timeauditLate-night lockon starting newworkRefereeno candidate haspassedThe charter's fourrules1The systemprepares; Idecide.2Nothingirreversiblewithout myapproval.3Only verifiedfacts enter thevault.4Every numbercarries a sourceand a date.1Interfacesafter every turn a fast model proposes the open itemsit heard, each with a quote; code drops any quote notin the turn2Orchestratorchecks what comes inMemory, workers, stores3MEMORY4WORKERS5STORES6Routines13 scheduled jobs7Auditchecks on the system itselfDesktop appWindows PC andMacTelegramon my phoneVoice modeOne agenton a large hosted model; the only part that writesAlways-onnotesa short notefile and aprofile, inevery turnFact store19 facts,searched whenneededSkills120 files forrecurring workNotes vaultthe long-termrecord; ActiveThreads openseach sessionWorkeragentsin parallel,each with aclean contextKanban boardmulti-stepworkSessionledgerinbox: toTodoist ordroppedTodoistthe one tasklistNight planner06:00;proposes,writes nothingyetReviews,reminders,watchers,digestsand a buildmonitorSunday reviewthis weekagainst thelastQuote checkPlannervalidatorSession-timeauditLate-nightlockon starting newworkRefereeno candidatehas passedThe charter's four rules1. The system prepares; I decide.2. Nothing irreversible without my approval.3. Only verified facts enter the vault.4. Every number carries a source and a date.
FIG. 1One path through the system. Seven layers on one Linux machine at home, with two trips through them: an item heard on the phone, and a piece of research a worker proposes. Dashed boxes do not act yet: the night planner runs in shadow mode, and no referee has passed its bar.
Source: How I run my life sheet, Architecture (round 4 text); orchestrator charter (sources.md)

One agent is the only part that writes, and its charter starts with the rule that the system prepares and I decide. After every turn a fast model proposes the open items it heard, each with a word-for-word quote, and code drops any whose quote is not in the turn. A worker's "done" counts only with a file path, a URL, command output or an exact quote.

The night planner proposes where slipped tasks go in free calendar blocks, and a script checks every move. For now nothing gets written (shadow mode). The last audit check, the referee, is meant to catch the agent claiming work it did not do.

Measuring the effect

TIME ON THE SYSTEM71%mid August to late September 2026,setup50% withoutlinks and videosshould fall · monthlyOPEN LOOPS ON ME395 Nov 2026, 30 of them mine0 after a cleanup on 24 Octshould fall · weeklySLIPPED COMMITMENTS15 Nov 20264 on 27 Oct5 to 11 a morning, to 4 Novshould fall · daily, readweeklyPROPOSALS STOPPED BY CHECKS4of 1,267quote check, since 19 Octplanner validator: 0 of 66 moveswatch: a zero needs a secondlookROUTINES HELDnot measured yetmy 4 basic routines, against theweek beforeshould rise · weeklyHOW TO READshould fallshould risewatched both waysTIME ON THE SYSTEM71%mid August to late September 2026, setup50% without links andvideosshould fall · monthlyOPEN LOOPS ON ME395 Nov 2026, 30 of them mine0 after a cleanup on 24 Octshould fall · weeklySLIPPED COMMITMENTS15 Nov 20264 on 27 Oct5 to 11 a morning, to 4 Novshould fall · daily, read weeklyPROPOSALS STOPPED BY CHECKS4of 1,267quote check, since 19 Octplanner validator: 0 of 66 moveswatch: a zero needs a second lookROUTINES HELDnot measured yetmy 4 basic routines, against the week beforeshould rise · weekly
FIG. 2The rubric, first readings. Each reading with the direction it should move if the system helps. The first three should fall; the fourth watches the checks themselves.
Source: How I run my life sheet, rubric table; session ledger and night planner records, queried 2026-11-05 (sources.md)

An audit in early October gave the first measurement: in my first six weeks on Hermes, 71% of my active session time went into building and running the system instead of my own work. One rater sorted the sessions, so the figure is rough, and those weeks were setup, when a high share is expected. I treat it as a starting point, to re-measure the same way.

It is one row of a working rubric where every row already has a data source:

Dimension What is measured Source
Time on the system Share of active session time spent building or running the system Session history, sorted by topic
Open loops on me Open items waiting in the session ledger Session ledger
Slipped commitments Dated tasks past their time, counted each morning Night planner
Proposals stopped by checks Items thrown out by the quote check; planner moves rejected by the validator Session ledger, planner results
Routines held How many of my 4 basic routines met their own floor, against the week before Sunday review

I count rejections because a check that never says no might not be looking.

What did not hold

5 Mar 2026Vault goesinto git; thesystem starts14 Aug 2026First sessionon HermesAgent5 months5 Oct 2026Audit: 71% ofsession time;jobs cut from11 to 67 weeks24 Oct 2026Rulesapproved;ledger clearedto 03 weeks25 Oct 2026Night plannerinstalled, inshadow1 day30 Oct 2026Due: decidewhether theplanner maywrite5 days5 Nov 2026Still inshadow6 days5 Mar 2026Vault goes into git; the system starts5 months14 Aug 2026First session on Hermes Agent7 weeks5 Oct 2026Audit: 71% of session time; jobs cut from11 to 63 weeks24 Oct 2026Rules approved; ledger cleared to 01 day25 Oct 2026Night planner installed, in shadow5 days30 Oct 2026Due: decide whether the planner may write6 days5 Nov 2026Still in shadow
FIG. 3Seven months, and one decision still open. The build ran for months before the first measurement. The hatched date is a decision that was due and has not been taken.
Source: project.json timeline; How I run my life sheet, What did not hold

After the audit I cut the scheduled jobs; they have grown back, not all for this system. The quote check threw out few invented items; more noise came from the agent's own offer to go through items one by one, captured 18 times. On the day the rules were written, the agent labelled them approved before I had said yes. The planner is still in shadow, past the date when the decision on letting it write was due.

Open question

For anyone who measures what tools change in people's lives: most of what this system should change happens outside a chat session, where my audit could not see it. How would you measure that part without logging the rest of my life?

← Referee model race · all lab sheets · PInspect →