Home / Lessons / Set the boundaries / 13 of 27
Anatomy of an AFK run
It starts with a contract and ends at a gate. Nothing in between merges without my yes.
I start the run with one batch of decisions and a contract. The contract sets scope, permissions, permanent fences, a budget, stop conditions and exit tests.
The lead agent coordinates separate lanes for building, testing and collecting evidence. The lanes write to shared state. If one lane needs a credential or a decision from me, that lane stops. Safe, independent work carries on.
The work rejoins at independent review. Failed review goes back to implementation. Passing work produces an evidence pack and a draft pull request. Then the run stops at the merge gate and waits for me, unless I gave that yes in writing before it began.
Nothing reaches production any other way. Being away changes when I supervise. It does not change what I own.
How I do it
Five or six hours, one contract in, one draft pull request out.
The rule
Design the run so the most it can do without you is prepare a decision, or carry out one you granted in writing before you left.
Rule 13. Design the run so the most it can do without you is prepare a decision, or carry out one you granted in writing before you left. (Anatomy of an AFK run, https://chiefofagents.si/one-page#rule-13)
The skill I use for this: /never-block-on-the-human. Made by Lauren Tan.
Read next
The ideas behind it
- What is an AFK run?A bounded stretch of unattended agent work, with a written contract at the start and a human gate at the end.
- What is a run contract for an AI agent?A short written agreement that sets what an agent may change, what it may never do, and what proves it is finished.
- What is a human gate?A protected action that cannot go ahead until an authorised person approves it.
This lesson as plain text, for your agent. Or all 27 on one page.