Updated just now.
2026-09-12 — Tonight the household web app got the voice Nick chose: a front desk that starts talking in about one second and asks the main assistant program behind the scenes for anything that needs his real records, measured live on ten spoken turns on 2026-09-12 at 22:44 UTC. The main assistant program's per-turn load was measured with Anthropic's own token counter at 124,932 tokens, two thirds of it Nick's health record injected whole on every turn; the health engine session then made the health engine the only door for health answers and cut that block down to the six safety rules about his body, so each turn now reads 24,555 tokens from cache instead of 107,691. The remaining per-turn cost is the 42 tool definitions, about 17,000 tokens re-sent on every turn because the subscription route this program uses to reach the model can only remember one fixed block of text between turns; trimming those definitions is waiting on Nick's yes. Earlier tonight: when Nick said out loud that a Sonnet coding agent should write a test file, a real Sonnet coding session started on his Mac Studio within two minutes of his confirming tap and wrote that file, so the spoken start-a-coding-agent door works end to end; Chantelle's assistant now runs on the main assistant program in the cloud after Nick approved setting her sign-in secret; all six live tests that Nick and Chantelle each meet their own assistant and never the other's pass; and Nick chose three AI-style faces for the Slack profile pictures, held until he says go. Two items need Nick: a yes to trimming the tool descriptions, and running one command from his own terminal to switch off the safety lock that stops agents editing the assistants' rule documents until 2026-09-13 at 12:44 UTC, so six of those documents can be created and one wrong sentence removed from the file that describes Chantelle's assistant.
2026-09-12 — Six pieces of the project that turns Nick's three AI assistants into one clean system are finished and independently checked. One: a spoken or typed yes from Nick keeps a fact the assistant offered to remember, exactly as pressing the Keep button in the app does. Two: the phone's remember-this command will stop being refused, because the assistant's cloud program now hands each memory to the Mac program, where the program that checks for passwords and keys before saving actually runs. Three: every publish of the assistant's cloud program now runs a guard that proves the assistant's standing instructions are being reused between turns instead of re-sent. Four: it is proven, and guarded by a test, that no automated job messages Nick from the Slack account of Chantelle's assistant. Five: the routing code that decides which text may go to cheap AI models now says exactly what Nick ruled: family, kids, health and client text travel; only logins, keys, government ids and card, bank and routing numbers stay home, and no old wording is kept anywhere in that file. Six: it is measured twice that a coding session started in the background by a job never appears in the list of running sessions the assistant reads aloud, so the new start-an-agent command will register each session it starts. Pieces one, two, three and five live in the cloud program's code and are being published to Nick's phone right now; four and six needed no publish. Still building: the module and wiring behind the spoken start-an-agent command, the seven draft documents describing the three assistants (five of seven written), the three avatar images redrawn to exactly the shapes an independent design review specified, and the second run of the measured comparison between two ways of building a spoken back-and-forth conversation with the assistant, this time with network access allowed.
2026-09-12 — Six pieces of the project that turns Nick's three AI assistants into one clean system are finished and independently checked. One: a spoken or typed yes from Nick keeps a fact the assistant offered to remember, exactly as pressing the Keep button in the app does. Two: the phone's remember-this command will stop being refused, because the assistant's cloud program now hands each memory to the Mac program, where the program that checks for passwords and keys before saving actually runs. Three: every publish of the assistant's cloud program now runs a guard that proves the assistant's standing instructions are being reused between turns instead of re-sent. Four: it is proven, and guarded by a test, that no automated job messages Nick from the Slack account of Chantelle's assistant. Five: the routing code that decides which text may go to cheap AI models now says exactly what Nick ruled: family, kids, health and client text travel; only logins, keys, government ids and card, bank and routing numbers stay home, and no old wording is kept anywhere in that file. Six: it is measured twice that a coding session started in the background by a job never appears in the list of running sessions the assistant reads aloud, so the new start-an-agent command will register each session it starts. Pieces one, two, three and five live in the cloud program's code and are being published to Nick's phone right now; four and six needed no publish. Still building: the module and wiring behind the spoken start-an-agent command, the seven draft documents describing the three assistants (five of seven written), the three avatar images redrawn to exactly the shapes an independent design review specified, and the second run of the measured comparison between two ways of building a spoken back-and-forth conversation with the assistant, this time with network access allowed.
2026-09-12 — Four pieces of the project that turns Nick's three AI assistants into one clean system are finished and independently checked. Piece one: a spoken or typed yes from Nick keeps a fact the assistant offered to remember, exactly as pressing the Keep button in the app does. Piece two: the phone's remember-this command will stop being refused, because the assistant's cloud program now hands each memory to the Mac program, where the program that checks for passwords and keys before saving actually runs. Piece three: every publish of the assistant's cloud program now runs a guard that proves the assistant's standing instructions are being reused between turns instead of re-sent, which is what made the assistant slow and expensive on 2026-09-12. Piece four: it is proven, and guarded by a test, that no automated job messages Nick from the Slack account of Chantelle's assistant; the two jobs that once did were repointed in July, so anything for Nick comes from the Slack account of Nick's own assistant. Pieces one, two and three live in the cloud program's code and reach Nick's phone only when that program is next published, which happens once the pieces still editing the same code file land; piece four is already in effect because nothing needed changing. A fifth piece, the change that lets family, kids, health and client text go to cheap AI models while only logins, keys, government ids and account numbers stay home, passed its checker on everything except one wording fix, which has since been made and is being re-checked. Still building: the wiring that makes the cloud program read each assistant's own rule documents, the module behind the spoken start-an-agent command, the seven draft documents describing the three assistants, the three avatar images redrawn to exactly the shapes an independent design review specified, and the second run of the measured comparison between two ways of building a spoken back-and-forth conversation with the assistant, this time with network access allowed.
2026-09-12 — Three pieces of the three-assistants build are finished and independently checked. A spoken or typed yes from Nick keeps a fact the assistant offered to remember, exactly as pressing the Keep button in the app does. The phone's remember-this command will stop being refused: the assistant's cloud program now hands a memory to the Mac program, which holds the credential checker, instead of refusing because the checker is missing in the cloud. And every time the assistant's cloud program is published, a guard asks it one tagged question and reads that request's own cost rows from the cloud server, so the slow-and-expensive problem of 2026-09-12, where the prompt cache was thrown away on every turn, can never come back unnoticed; today's live reading shows the cache being reused. None of the three is on the phone yet: one publish of the cloud program carries all three, and it waits for the routing-wall change that is finishing now. Seven other pieces are in flight: the code that lets each assistant read its own rule documents, the module behind the new spoken command that starts a coding agent, the routing-wall change that lets family and health text go to cheap AI models while only logins, keys, government ids and account numbers stay home, the seven draft documents describing the three assistants, the three avatar marks drawn in code, the measured comparison of ways to build a real spoken conversation with the assistant (OpenAI's Codex tool, second attempt with network allowed), and the read-only file auditor's first pass, which came back with four grouped findings that wait on the rule blocking new documents until tomorrow midday.
2026-09-12 — The plan for making Nick's three AI assistants (Skippy for Nick, Gracie for Chantelle, Neeko for the business team) into one clean system passed its three reviews today: an automatic checker script, a cold attack by OpenAI's Codex tool, and a fresh reviewer session, and every point they raised is fixed in the plan. Building has started and the first piece is finished and independently checked: a spoken or typed yes from Nick now keeps a fact the assistant offered to remember, exactly as pressing the Keep button in the app does. Nine other pieces are being built at the same time: the code that lets each assistant read its own rule documents; the module behind the new spoken command that starts a coding agent; the change that lets family, kids and health text go to cheap AI models while only logins, keys, government ids and account numbers stay home; a guard that catches the assistant's prompt cache silently breaking again; the seven draft documents describing the three assistants; the three avatar images; the measured comparison of two ways to build a real spoken conversation with Skippy, done by OpenAI's Codex tool; the first pass of the read-only file auditor; and the fix so the phone stops refusing remember-this. One rule of the road surfaced: the cheap models are not allowed to read the assistant's main code file because it contains a credential-shaped line, so edits to that file run on Anthropic's Opus model, one at a time, on Nick's own words from 2026-09-05.
2026-09-12 — A build plan now exists for making Nick's three AI assistants (Skippy for Nick, Gracie for Chantelle, Neeko for the business team) into one clean system, and an automatic checker script confirms it is complete. Nick answered three open questions today: a spoken yes is enough to keep a memory; the assistant asks which kind of agent to start when Nick does not say which; and this project's task card at hub.heroesandsidekicks.io is due 2026-09-13. OpenAI's Codex tool is reviewing the plan for ambiguities, and a separate fresh reviewer session reads it cold next; building begins after both reviews. One measurement is already done: a Claude Code work session started in the background by a scheduled job does not appear in the list of running sessions that Skippy reads aloud, so the new start-an-agent feature must record each session it starts.
Definition of done: the document loader is live for all three assistant faces, Neeko's hard-coded prompt copies are gone from the cloud brain's code, and a marker sentence added to each assistant's the relevant record file is read back by the live cloud brain within 35 minutes
Proof: node the relevant record prints ALL PASS; grep STANDING_RULES_NEEKO in the relevant record counts 0; the live-drive evidence file shows the marker sentence in all three assistants' answers
Verified: not yet — the plan was written on 2026-09-12 and its independent cold review is in progress
Definition of done: the evidence file states, from literal output with a real pid, whether a job-started headless session appears in the live per-machine running list within 150 s
Proof: evidence/step2-the relevant record (pid 87390): SESSIONS_DIR does not appear, SOCKET does not appear, TRANSCRIPT written, WORK_THREADS_LIVE not listed; the verify tool reproduced the in-tree pairs and the checker re-ran the four outside-tree ones by hand
Verified: 2026-09-12 (100%, checked by the haiku exerciser in its own session; evidence/step2-the relevant record)
Definition of done: on a box without the credential scanner, a memory proposal is scanned and stored pending on the Mac, never refused and never stored unscanned
Proof: node the relevant record prints ALL PASS with the three route cases, and the relevant record stays green
Verified: 2026-09-12 (100%, checked by the haiku exerciser in its own session — 37 of 37 and 25 of 25 re-run first-hand; evidence/step9-the relevant record)
Definition of done: a person's yes to a named pending fact lands the row in the confirmed file; a model-side affirmation still does not
Proof: node the relevant record prints ALL PASS including the new case, with the red run saved in the plan's evidence folder as the relevant record
Verified: 2026-09-12 (100%, checked by the haiku exerciser in its own session — 44 of 44 PASS re-run first-hand, the old header gone, the red run on file, the commit scoped to three files; evidence/step10-the relevant record)
Definition of done: no job sends a message to Nick through the Gracie token; the test that proves it can go red
Proof: node the relevant record prints 0 send sites to Nick via the Gracie token and 4 sites reaching Nick as Skippy, exit 0; a sabotage fixture makes it print 1 and exit 1
Verified: 2026-09-12 (100%, checked by the haiku exerciser in its own session — re-run on 205 job files, sabotage fixture red, two historical sites confirmed as comments; evidence/step13-the relevant record)
⚠️ only 1 of 2 required verifications recorded so far
Definition of done: The voice path Nick chose (a realtime front desk that answers at once and asks the main assistant program behind the scenes) speaks its first word in under two seconds on ten of ten spoken samples.
Proof: The measurement harness, run live against the deployed household web app on 2026-09-12 at 22:44 UTC, printed ten samples with first audio between 1,041 and 1,992 milliseconds; an independent checker on a separate model is re-running it now.
Verified: Sixteen of the plan's twenty-six steps are closed with an independent check each (steps 1, 2, 3, 4, 5, 8, 9, 10, 11, 13, 14, 16, 18, 20, 23, 25). Step 17 is built and live with its checker running. Step 6 (a spoken request starts a real coding agent) worked end to end on its second run. Step 15 (talking to a running thread from the Status tab) is deployed with delivery proven live; its spoken half waits for an idle session to answer.
Definition of done: the routing code enforces exactly the floor and nothing else, proven by a test that was red against the old code
Proof: node the relevant record prints ALL PASS 126/126 on both copies; each copy's own selftest blocks every private-to-cheap-vendor case; red run in evidence/step23-the relevant record
Verified: 2026-09-12 (100%, checked by the Sonnet verifier in its own session — first check failed on kept old wording, fixed, re-check PASS; evidence/step23-the relevant record and the relevant record)