The Harness
Standing instructions
House rules written once, read by the machine every session. The end of repeating yourself.
Every correction you write in chat evaporates with the session. A standing instruction does not: a rules file, a project brief, a saved preference, a custom instruction is read by the machine every single time, without you spending a word. This is where the fourth law cashes out. The correction you were tired of typing becomes a line in a file, and the failure class it addressed stops recurring, quietly, forever.
A good rulebook is small, specific, and earned. Every rule should trace to a real incident, name the failure it prevents, and say how to comply. Rules nobody triggered in months are noise that buries the ones that matter, and a rulebook the machine cannot finish reading is a rulebook it will not follow. Scope rules to where they apply, and prune like you mean it.
How to practice it
One incident, one rule.
When a correction repeats, write it down where the machine reads it every session. Date it, name the failure, state the fix.
Say why, not just what.
A rule with its reason survives being questioned and gets applied to cases you didn't foresee. A bare prohibition gets lawyered.
Scope to the territory.
A rule about one project's quirks loads only there. Global rules are for laws; local rules are for terrain.
Prune quarterly.
A rule that no longer fires is either won or wrong. Retire it; the survivors gain weight from the trimming.