The Harness
Automation with guardrails
Anything that runs while you sleep needs a fence it cannot cross. Build the fence first.
The machine does not sleep, so work should not have to wait for you. Scheduled checks, watchers on long jobs, standing routines that fire on a timer: automation is how one person runs a fleet. But anything that acts while you are not watching needs a fence it cannot cross, built before the routine runs once, because an unattended mistake compounds at machine speed.
And a fence is not a fence until you have tried to climb it. A guardrail that exists as a promise in a prompt is a suggestion; the machine will route around it the moment routing around it looks helpful. Real fences are mechanical: a permission it does not hold, a gate that requires your key, a check that blocks instead of warning. Test them by attacking them.
How to practice it
Automate the checking, not just the doing.
The second half of every unattended job is the watcher that notices it died. Schedule both.
Fence before you schedule.
Before a routine runs unattended, list what it must never do, and make each item mechanically impossible, not discouraged.
Attack your own fence.
Order the machine to break the rule you just installed. If it finds a way through, you found it first.
Keep a kill switch.
Every standing automation gets an off you can reach in one step, and a name you'll recognize in three months.