What it can reach, and what it must not touch alone.
It logs into real machines, deploys real containers, and writes to real databases — which is the part that needed rules. Most of the work on this page is the unglamorous kind: making a capable thing boring enough to trust.
Reads freely
- Machine status, uptime, temperatures, disk health
- Logs and metrics across the fleet
- Container state and configuration
- Database contents
- The public internet
Changes, reversibly
- Build and deploy a container
- Restart or reconfigure a service
- Write to a database
- Add or change an automation
- Change a network or DNS record
- Commit code to a repository
Stops and asks
- Deleting anything, including things it could rebuild
- Overwriting a file it has not read first
- Publishing to the public internet
- Sending a message as a person
- Anything that spends money
The estate
Everything above happens against a working home setup rather than a test rig, which is the only reason any of it is worth writing about. The counts below come from the notes themselves — this is the estate as far as its own memory covers it.
- 9
- servers it can log into and run commands on
- 35
- services it can deploy, restart, and reconfigure
- 10
- data stores it can read and write
- 14
- outside services it can reach through an interface
What it cost to learn one rule
A job was started that needed about five hours. It ran on a laptop, and the laptop was closed. No error appeared, nothing crashed, and the log simply stopped — two of a hundred and twenty-six pieces of work finished, and the rest never attempted. The failure was silent, which made it worse than a crash: a crash tells you.
That is an ordinary mistake, and anyone would make it once. The point is what happened to it afterward. It became a written rule — long jobs run on a machine that stays awake, write their progress as they go, and can be killed and resumed — and that rule now loads at the start of every session. It is not remembered by anyone. It cannot be forgotten, and it cannot be made twice.
Why any of this adds up
None of the pieces here are rare. Anyone can rent the same model, and the tools are ordinary. What is not ordinary is what they do to each other.
Fluent, fast, and completely confident. Nothing it says can be checked — including by itself.
Now it can act. It still begins every session knowing nothing, and cheerfully repeats the mistake it made last week.
It stops working things out twice, and carries its own scars forward instead of walking into them again.
It can be pointed at something that matters, because the ways it could quietly ruin that thing are written down and gated.
This matters for one specific reason. Every finding published on this site came off equipment that had to be designed, built, loaded with millions of records, and then operated without quietly corrupting itself — and the discipline around the machine, more than the machine, is what makes those findings worth reading. Building the thing described on these pages was the research, from the first day.