Loop Contracts
# Loop contracts (full, machine-readable specs)
A **loop contract** is the whole loop written down as data: goal, trigger,
intake, workspace (and what's *off-limits*), verification gates, memory, budget,
escalation, and exit. Writing the contract first is the single best way to make
a loop safe to run unattended — it forces you to answer "when does this stop?"
and "what may it never touch?" before you turn it on.
→ Background: [docs/03 — Anatomy of a Loop → The loop contract](../docs/03-anatomy-of-a-loop.md#the-loop-contract).
> The shape below is this repo's own contract schema. Treat each example as a
> template: copy one, change the fields, delete what you don't need.
---
## The contract shape
Every contract answers the same questions:when to use it
Community prompt sourced from the open-source GitHub repo invincible04/awesome-loop-engineering (MIT). A "Loop Contracts" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
invincible04/awesome-loop-engineering · MIT