01 / BRIEF
An always-on engine, a router, an agent that answers on chat, and workers picking tasks off a board. Two machines share a single git repository as their message bus, syncing every fifteen minutes.
The fleet exists to buy back attention. Every recurring thing that used to need a human in the loop, filing a task, checking a system, noticing that something went quiet, now happens without one. What is left on the bench is the work that actually needs judgment.
It is also the place where every idea about building with agents gets tested before it goes anywhere near a client. If a pattern cannot survive running unattended on my own machines for a month, it does not deserve to be a recommendation.
02 / HOW IT WORKS
The bus. The cabin is a laptop that comes and goes. The engine is a machine in the corner of the room that never sleeps. Between them there is no queue, no broker, no service to keep alive: there is a repository, and both of them commit to it. Every fifteen minutes each side pulls what the other left. The bus is boring on purpose, and boring is what survives a bad week.
The eyes. A separate observation layer ingests the things that carry the real signal: several mailboxes, messages, the calendar, even sleep and recovery from a wearable. It writes them into an append-only event log with one cursor per consumer, so any reader can be rebuilt from scratch and replay history without asking anyone's permission. Seventeen small services, each one dumb alone.
The reflexes. Watchers react when something arrives instead of asking every few minutes whether anything has. A calendar change reaches the fleet in seconds, not on the next cron tick. The bottleneck was never the ingest, it was the reader.
The archaeologist. At dawn a miner reads yesterday's work sessions and files what fell through the cracks: tasks that got mentioned and never written down, decisions that never made it to a document, ideas worth keeping.
Everything the fleet does leaves a file behind. Not a log line in a service somewhere: a file, in a repository, with a commit. The whole system can be audited with git log, which means it can be trusted without being watched.
03 / DECISIONS
A model earns trust through its harness, not its weights. Small typed action space, a verifier the model does not control, and on failure a retry with the verifier's error pasted into context. Decomposing one hard question into three checkable ones beats asking it once, carefully.
Files over state. Anything a component knows is a file that another component can read. It makes every part replaceable and every failure visible, and it means the recovery plan for almost anything is git.
An append-only log with cursors, not a queue. A queue forgets. A log lets a consumer that was broken for three days catch up on its own, and lets a new consumer read history that predates it.
The mechanical work runs on a local model. Judgment costs money; sorting, extracting and classifying do not have to. A job that talks to the local model gets no tools at all: it answers with structured text, and the code does the acting. That constraint is what makes a small model reliable.
A job that fails must say so. Silent success is the most expensive bug in an unattended system: a broken job that reports "nothing to do" looks identical to a healthy one, and stays broken for days.
04 / STATUS
Running 24/7. It filed the task to build this site, and then it built it.