work-looplisted

# Work-loop — the cycle contract and its resumable ledger A Loop is bounded work with a declared contract, iterations that each end in exactly one of six outcomes, and a ledger a fresh session can resume from without repeating a single completed action. ## What this is not for | The task | Its owner | Why not this skill | |---|---|---| | Whether to keep going at all, and what to do next | `endless` | That is the continuation doctrine and its three checkpoints. This skill describes one cycle; it never decides whether another should start. | | Polling until a command goes green | `verification-loop` | A retry until an exit code flips needs no contract and no ledger. | | Executing a written implementation plan | `executing-plans` | The plan is the sequence. A Loop is a cycle with a limit. | | Recurring wall-clock scheduling | Not this skill, at all | Nothing here schedules, triggers, or wakes anything. | | What to work on next | `roadmap` | A Loop is *how* a bounded piece of work is run, never *which* work is next. | | Recording that a mid-run task displaced work, and what condition means the return is owed | `off-topic` | `pause` ends this cycle; a displacement suspends work inside a run that is still live, and often in a session that opened no contract at all. | | Deciding whether a defect found inside an iteration is fixed now or routed and left | `out-of-scope` | An iteration's scope is the contract's; that skill scores what to do with work outside it, and its deferral re