# 13. Anatomy of an AFK run

> It starts with a contract and ends at a gate. Nothing in between merges without my yes.

Lesson 13 of 27. Part 3 of 6: Set the boundaries. Source: https://chiefofagents.si/lessons/anatomy-of-an-afk-run

## The lesson

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.
