Execute

The vault has a resident operator. I call him the Butler: an unattended agent that wakes every thirty minutes, checks whether anything is pending, and if so runs one working cycle on my behalf. A gate script keeps empty ticks free; when he does wake properly, he runs on a cheaper model with a scoped tool allowlist that cannot send, publish, or spend. Everything around him is deterministic: code decides whether he wakes, what he may touch, and what gets logged; the model is only the judgement in the middle.

One cycle covers the whole machine. He sweeps any raw voice captures into finished notes, reads and acts on my answers to his open questions, classifies new tasks, runs the closure pass over anything that looks finished, checks every pipeline lane for failures, and writes up what he did.

Every task he touches gets classified, and ambiguity always demotes. A task he can do end to end is AUTO. A task where he can produce something useful for me to finish is PREPPED. Everything else is HERS, untouched. The tests are concrete: could this be done from the command line, and would a prepared artefact actually save me time? When the answer is unclear, the task moves down a tier, never up.

Hard gates override everything. Never send anything. Never delete without my word. Never publish externally. Never spend. Never touch the fields and sections that are mine alone. The content, email, and transcript lanes have their own judgement loops, and he stays out of them entirely.

He can repair the machine, within strict limits. When a pipeline lane breaks and the fix does not need me, he fixes it himself: config, thresholds, and templates only, backed up first, checked against everything that depends on them, and never twice for the same failure. The carve-out is precise: he may patch a lane's script, never its output. When the fix does need me, he asks instead.

Everything lands on two surfaces. Needs You is the single place anything wrong or waiting for me appears, anywhere in the system: his questions, prepared work ready for review, pipeline failures, unfiled counts. Claude Did is the audit trail, one block per cycle, and a Sunday job asks me to skim it weekly and calibrate him.

The trust is earned, and checked. He acts, the audit trail records it, I calibrate him weekly, and his rules absorb the corrections. Delegation with a paper trail, not delegation on faith.