What is a golden run?
golden run (n.) – the loop by which a procedure performed by a person becomes a procedure an agent can run unattended.
The loop has five movements. The procedure is executed once, end to end, by whoever knows it best, with every failure and hesitation recorded rather than smoothed over. The record is codified into a document in which each action carries two companions: a verify step, an observable check that the action took effect, and a recover step, the response when that check fails.
The document is then cold-verified by someone with no prior exposure to the work, running the document alone and adding nothing from memory. Whatever the cold reader stumbles over is a gap the author could not see. Finally the document is hardened: every constraint that must hold regardless of interpretation is moved out of prose and into code.
The distinction between a golden run document and a checklist is that pair of companions. A checklist states what to do. A golden run document also states how to know it worked and what to do when it did not, which is the difference between a procedure a person follows and a procedure a process executes. An agent, like any unattended process, does not notice that a step silently failed unless the document said what success looks like.
The loop does not end at hardening. Every run that produces a surprise produces an amendment, written while the surprise is fresh rather than at the end of the quarter. A procedure that has stopped generating amendments is either stable or unobserved, and the two are told apart only by checking.
mandate-ladder(7), company-as-code(7), removal-test(7), headcount-zero(7)
The failure the loop is built against
Most procedures are written from memory after the fact, which produces documents that work for their author and for nobody else. The author's knowledge fills the gaps invisibly at the moment of writing, and fills them again at the moment of rereading, so the gaps are never observed. Capturing failures during a live run, and then handing the result to a cold reader, are the two steps that make them visible. Both are commonly skipped, because both feel redundant to the person who already knows the work.
New entries
New entries and revisions go out by mail when they land. No fixed schedule, no announcements.
address recorded. new entries will be sent there.
No spam. Used only to send the notes.