loop

# The loop **Nothing is done until it has been observed working.** A green build, "I read the code and it looks right", and "this should work" are not verification. The only valid signal is observed behaviour. Run these six steps for every item. Do not skip 0 and do not skip 5. ## 0 · Locate yourself - Read `.loop/STATE.md` (what is done, what is next, what is parked) and `.loop/GOTCHAS.md` (traps this project has already sprung). - `git log --oneline -15` and `git status`. **Anything already committed is not rebuilt.** A lot of what a document calls missing is already built and just not visible — confirm against the code before redoing it. - Uncommitted files that are not yours may belong to a parallel session. Do not touch them, and do not reuse a shared counter they may have taken (see the shared resource in `.loop/VERIFY.md` — read its true state with the command declared there). - The next item is the first unchecked `[ ]` in `.loop/STATE.md`. You do not need new instructions to continue. ## 1 · Investigate Open the real files you are about to change. Map what exists, what is editable, what is missing. Never work from memory of an API or a schema. If a question is genuinely open — or the item touches money, permissions, auth, or schema — run the `loop-council` skill *before* writing code, not after. ## 2 · Build, completely One item at a time, finished. If completing it requires one more thing, that thing gets built too: it is not reported as a leftov...