loop-stopThe same command has now run 3x with no code change in between — a loop, not progress.
loop-stop — the same command run 3× with no code change in between is a loop, not progress; refused. Read-only commands are exempt (git status, ls, cat, grep, find and their kind), so looking at the same thing three times is never a refusal — only doing it is.
From README.md.
loop-stop: same non-read-only command, 3rd time, no code edit in between
From the comment in native/gate_pre.h above the code that decides it.
Rendered from the strings in native/gate_pre.h, the rule and the envelope (Judge::refuse) both. A word in <angle brackets> is filled in from the command at the moment it is refused.
Only the user can switch it off, by id, in the project's guard:
or by pausing supervision with rabadon off, which records the change. Every other rule keeps running.
9 of the 778 records in the published field dataset (field.jsonl, 2026-07-27 to 2026-08-26) carry this id. STOP is a refusal in enforce mode; WOULD_BLOCK is the same verdict recorded in watch mode, where nothing is stopped.
| event | records |
|---|---|
| WOULD_BLOCK | 7 |
| STOP | 2 |
Counted from field.jsonl, the file the field page is built from.