Nicholas Lipetzky.
Page 002 The machine register
Worked example: Ferncastle 2026.09.08

Sixteen things run without a person. Four of them can prove they ran.

A machine only runs without a person if five things are true of it. At Ferncastle the first three are true almost everywhere and the last two are true almost nowhere, which is how a watering alert stopped in August and the first thing to notice was the plants.

■Can prove it ran ■Written down ×Nothing written —Does not apply

How to read this. Every row is one thing at Ferncastle that runs without a person, named by what it does. Every column is one of the five things that have to be true before you can leave a machine alone: what starts it, how it picks its work, what it writes down, what it must never do, and how it proves it ran. A filled square means somebody at Ferncastle has written that part down. Hover or tap any square to read what it says.

The problem I had

We currently have an outreach system that is sending emails to electricians. However, I don’t know if that is sending the maximum amount of emails every day. I don’t know if we have the entire collection of contacts ready to go in the outreach base. Nick, 2 September 2026

I had built the thing so I would not have to touch it, and then I could not tell you whether it was doing its job. That is the whole trap. A machine that has quietly stopped looks exactly like a machine with nothing to do.

So I stopped asking whether the system works, which is unanswerable, and started asking five narrower questions about each machine, which are not: what starts it, how it picks its work, what it writes, what it must never do, and how it proves it ran.

What the picture shows

Sixteen machines, five questions, eighty squares. Three do not apply, because a machine that waits to be called has no scheduled run for anything to miss. The left of the picture is nearly full and the right of it is nearly empty, and that shape is the finding.

Everything at Ferncastle knows what starts it. Most things know how they pick their work and what they write down. Almost nothing has a written rule about what it must never do, and only four of the sixteen can prove they ran. All four of those are watched by a person who would notice within a day: the routes on eleven phones every morning, the billing run the controller reconciles against the bank, the invoice count the bookkeeper matches to the charge count, and the payroll 180 people are waiting for. Nothing on this picture proves itself to a machine.

Then there is the row with the flag. The alert that tells a technician a building is drying out stopped eighteen days ago. The sensors kept reporting the entire time, so every screen showing sensor data looked exactly as it should. Nothing was watching the alert itself. Plants died in three buildings before anyone worked out why.

What changed

The five answers stopped living in somebody’s head. Each machine now carries them as written fields on its own record, and a picture like this one is drawn from those records rather than from what anybody remembers. Change what a machine does and the picture changes with it.

The fifth question is the one that pays for itself. A machine that cannot prove it ran will one day stop without telling anybody, and the company will keep making decisions as though it were still running. Writing down how each one proves itself is what turns a silent stop into a message on a Tuesday.

The fourth question is the one people skip and then regret. On my own register, the machine that emails a stranger carries two written refusals, and both were written the night we found 2,346 people in a table who did not exist.

Where the data came from

Example
Ferncastle is a worked example: a fictional 180-person company that leases and tends office plants. Its sixteen machines, their five answers and the eighteen-day outage are invented to show the instrument. No client’s data appears on this page.
Source
The sixteen rows are the things page 001’s inventory marks as running on their own that actually do a piece of work, on a clock or on a trigger, so the two pages describe one company. Five more run on their own only in the sense that they are always up: the website, the vans’ tracking, the client portal, the shared drive and the password manager. A service that is simply on has no scheduled run to miss, so it is not on this picture. One row that is here, the plant-of-the-week post, sits on the inventory with no owner at all.
Real
The instrument is real and it runs my own business. Thirteen machines in one outbound pipeline, sixty-five parts, sixty that apply, and today all sixty are answered. One of those records is out of date, which I found by drawing this same picture of myself.
Method
A square is filled when somebody has written that part down, not when the machine behaves well. “Does not apply” means the machine is not on a clock, so there is no scheduled run for a watcher to miss. Every number on this page is computed from the data behind it, not typed.
Unfinished
A record holds what its machine says about itself. Nothing here checks that a written refusal is really enforced in the machine’s own code, so this picture proves the promises exist, not that they hold. And a machine with no record at all cannot appear on a picture drawn from records, which is the honest limit of the whole instrument.

The machine register, blank

The five questions as a sheet you fill for your own machines, the instructions for filling it, and a prompt you paste into whatever AI you use so it interviews you through it.

 

Work with me