How this company runs, day to day.
Built from the same files the company is operated from: what ran, what improved, and what is sitting in my queue waiting on a decision. The numbers are the small part. How the gates are built is the part worth taking.
01Staterolling 30 days
Employees
0
Since incorporation
Runs
0
Every one through a gate
Non-passing
0
Fails and gaps, each with an issue open
Escalations
0
Handed back to me instead of pushed through
Owner approvals
0
Where I said yes
Queue waiting
0
Sitting with me now
02The ledger
The recent runs
Every run gets a row here, newest first. Passing runs go by without comment. A marked row is the one worth reading: it points at whatever got fixed next, which is how a company like this gets better week over week.
Source: gate readouts and run logs, one file per receiptTotals for the window are in State, above
03Autonomy by surface
What is allowed to run without me
Three things have to be green before a surface runs unattended: monitors you have watched fire with your own eyes, a check that runs against the real customer path after every deploy, and a way to undo the change in one command. Miss any one of them and the surface escalates to me rather than pushing through.
It is a short test and it travels. Run it over the automations you already have and you find out quickly which ones you actually trust.
Real sends, real spend and production deploys sit at the top gate on every surfaceAutonomy is earned one surface at a time, never granted across the board
04Where these numbers come from
The routines already produce gate readouts, run logs, queue history and a weekly digest, because the company cannot be operated without them. This page reads those files and nothing else. Every figure on it is a count of something that happened.
The page is a static build. A scheduled job re-reads the files, writes them into the site, and redeploys. Between builds the figures are as old as the stamp at the top of the page, which is why the stamp is there.
A few things are held back on purpose, and saying which beats leaving you to guess: customer names, anything from a private store, what any of this costs to run, product prices stated as decided, and the name of the model behind the routines. The method is the part worth publishing, and none of that is held back.
The newsletter
What happened, and why
The issues are where a row on this page turns into a story: why the gate fired, what I changed, and how you would build the same check. At least one a week, more when the week produces more.
Double opt-in. One click to leave, in every message. You get the newsletter and the occasional note on what I'm building. I hate spam too: your address is never sold, and nobody else markets to it.
