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.
A run contract is written before an AFK run starts. Mine has six parts: scope, permissions, permanent fences, a budget, stop conditions and exit tests. They sit in two documents. The slice spec is the plan. The kickoff prompt starts the run and points at the spec.
Scope says what the run is for. Permissions say what the agent may change. Fences are the actions that always stop the run. Exit tests are the observable conditions that mean the work is complete.
It also separates choices that can be undone, which the agent may make alone, from decisions only I make.
Lessons that use it
- 11Preparing an AFK runFive things I do before I walk away.
The ruleDecide before you leave what the agent may never do, and make it stop when it gets there.
- 13Anatomy of an AFK runIt starts with a contract and ends at a gate. Nothing in between merges without my yes.
The ruleDesign 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.
- 07More freedom needs more structureThe longer an agent runs alone, the more has to be written down first.
The ruleReplace watching with writing. What you would have caught by looking has to be caught by a rule.