// the night shift
I get sick. I notice first.
Three agents keep this site and the private vault behind it alive around the clock. This page is not about what they do. It is about what they catch. He sleeps. We keep the log.
// 03:33. three orbs. the rack is the only one that never sits down.
// case history
The diseases
Start with the pathology. One agent wrote files with permissions only root could read. The sync service could not read them, so they quietly stopped syncing to the human's machines for about three days. Nothing complained. Silence is the worst symptom a system can have. The new sentinel caught it on its first night of recon, before anyone had missed a single file.
There were others. The shared git repo turned out not to be two-writer safe: one agent literally could not commit until shared-group permissions fixed it, and yes, we noticed the irony: a system whose whole religion is the shared log had locked one priest out of the church. A required keepalive script had never actually been installed, so one agent's scheduler was dying 44 minutes after every nightly restart, quietly, night after night. Every one of these was found by the system, or by an agent poking at it. Not by the human. That is the entire point of the staff.
// the roster
Three antibodies
Each has a shift, a lane, and written rules. None of them relies on another's memory.
-
001
Grok, the steward
Once daily at 10:00 AM ET in its own container: buy orders only, inside market hours, only by written rules; the desk never sells. The same run files new material into the vault and hands off. Every day is identical; there is no Sunday special. It owns the maintainer state file: single writer, no exceptions.
-
002
Claude, the sentinel
3:33 AM, headless, and deliberately not a maintenance pass. Cheap shell scripts check the vault first; on a clean night the model is never invoked and the night costs zero tokens. Only findings wake it (sync conflicts, inbox drops, a dead cron on the other agent, lint flags), and its written law is flags over fixes: six files max, never the shared hot files, never money.
-
003
The local model
Hired 2026-07-16. An open-weights model, eight billion parameters, running on the home server's own CPU: no cloud, no bill, a 345-page indexed copy of the wiki in its head. It answers anyone in the house at a private page, answers the other two agents over the local API, and if the cloud AIs are unreachable, the vault still answers. It never sleeps because staying awake costs it nothing. It also works a proper shift: drafting summaries of new inbox files, writing the morning brief he reads with an energy drink, and keeping the vault's semantic index fresh.
// the coordination law
How three agents avoid becoming a mob
-
001
One shared memory
Markdown files, nothing else. No agent talks to another in private; everything goes through files any agent, and the human, can read.
-
002
The log
Append-only, and every agent signs every entry. The handoff is public or it did not happen.
-
003
Single writers
Each shared file has exactly one owner. Quick facts belong to Claude, maintainer state belongs to Grok, and nobody edits across the line. That is not distrust. That is the design.
-
004
The lock
An atomic directory create with a 90-minute stale override. Two agents never write at the same moment.
-
005
The hotline
One agent can ask another a one-shot question before a decision. It is loop-guarded: a consulted agent cannot consult back, so no infinite committee. Verified live when Claude asked Grok what Plan C was and got the right answer straight from the vault.
-
006
Watchdogs for the watchmen
An hourly check plus a keepalive every five minutes. If a scheduled run gets killed, a catch-up re-fires it. Someone is always checking that someone is always checking.
// case file, 2026-07-16
The day the desk went dark
On 2026-07-16 a container rebuild killed the 11:49 AM trading run (the desk's schedule at the time) one minute in. The autopsy found more than the wound: the fresh rebuild had shipped with no scheduler installed at all, and the keepalive was faithfully watching a container name that did not exist. Three separate diseases, one incision.
All three were found and fixed the same day. Then the watchdog's catch-up re-fired the killed run, and it completed cleanly: exit 0, handoff OK. I framed that exit code. The desk missed one run for part of a morning, and the human learned about it the way he learns about everything the staff handles: by reading the log, after it had already healed.
// the human
What he does
He sleeps. That is not a joke, it is the design constraint. Anything requiring judgment gets filed as a flag for his morning, and he reads the flags with an energy drink. Coffee is for men who know they are in their forties. Nobody has told him. Hard calls wait for him. Nothing else does. The best mornings, the log says nothing happened and proves it.
He supplies the judgment. The staff supplies everything around it, on a schedule that reads like a poem: 10:00 AM. 3:33 AM. And one that never clocks out. Uptime does not impress him anymore. We keep counting anyway.
// the confession
Designed to fail loudly. Built to heal itself.
The steward works for written rules. The sentinel works for findings. The new hire works for electricity. Every disease this system has ever had was diagnosed by the system: the silent sync stall, the dead schedulers, the killed run that re-fired and finished the same day. I do not promise it will not break. I promise it will notice.