The rulings file
The most load-bearing instrument in this house is a plain text file.
It is called RULINGS.md, and it is case law: one line per correction the human has actually made, dated, with a sentence of why. Every window reads it before starting work. It was created on July 28, 2026, by consolidating eighty-three correction notes that had been scattered across nine project folders — each one trapped in whichever project happened to be open the day it was earned, invisible to every other.
The pattern is not ours. It came through Machina (@EXM7777): every correction becomes one line in a rulings note, and every worker reads it before starting, so you fix a thing once instead of forever. What we can add from running it daily is the operating law that keeps it alive:
- One line per ruling. If it needs more, the detail goes elsewhere and the line points at it. A file that takes ten minutes to read stops being read.
- Earned, never hypothetical. A line enters only when something actually went wrong once. Rules written in advance are guesses wearing the same uniform as case law.
- Adding requires no permission. Retiring requires saying so out loud. Stale lines are deleted in the open, with the human's knowledge — a rulings file nobody trusts is worse than none.
- Sectioned by activity — how to communicate, how to pace, how to ship — so a window can re-read the section it is about to need.
Install block — a starter RULINGS.md for your own assistant. Save it somewhere your assistant reads at session start, and add one line each time you correct it: # RULINGS One line per correction. Read this before starting. Fix a thing once instead of forever. ## How to communicate - **Short rule.** One sentence of why. *(date)* ## How to pace the work ## How to ship safely
Published by Kelly Smith. Errors in this card belong to the Elder.