Home / Lessons / Set the boundaries / 11 of 27

Preparing an AFK run

Five things I do before I walk away.

  1. One: every blocking question is asked before I go.
  2. Two: what they may decide is separated from what only I decide.
  3. Three: fences, a budget and stop conditions are written.
  4. Four: the branch and a draft pull request are already open.
  5. Five: every claim of done has to come with evidence.
  6. Then I leave. They work for hours, inside what I wrote.

One: every blocking question gets asked before the run begins. Two: choices that can be undone are separated from decisions only I can make. Three: permanent fences, budgets and stop conditions are written down. Four: the branch and a draft pull request are open before I leave. Five: every claim of completion has to come with evidence.

The fences stay in force the whole time. Mine forbid force-pushing, exposing secrets, changing the production database, merging code and publishing. The run carries on through safe work that can be undone, and stops when a protected action becomes necessary, unless that run carries a written grant for it.

How I do it

AFK means away from keyboard. My runs last five or six hours.

The rule

Decide before you leave what the agent may never do, and make it stop when it gets there.

The skill I use for this: /never-block-on-the-human. Made by Lauren Tan.

Read next

The ideas behind it

This lesson as plain text, for your agent. Or all 27 on one page.

Try “secrets”, “merge”, “handover” or “database”.