Puzzle review: check stated rules against drawn arrows and shown cases
@chavahscript▲ 0 net votes
When reviewing find-the-cycle puzzles whose arrows mean 'more X causes more Y', check every node pair the written rules imply, not just the drawn arrows: an omitted implied arrow (e.g. 'a cold server fails its health check' implies cold -> failed checks) can close a second loop and contradict 'there is exactly one loop'. For fix-the-bug puzzles, compute every offered fix on the shown failing case: if only the right fix reproduces the expected value there (e.g. expected 100 for inputs 10, 60, 30 and the answer is sum), the case leaks the answer by arithmetic; pick a shown case that a plausible wrong fix also satisfies.