erc-reviewlisted

# Reviewing an ERC draft You are reviewing a proposal that a panel will read once, under time pressure, looking for a reason to stop. Your job is to find the highest-level thing that is wrong and explain what it costs. The rules live in `references/ERC_writing_guide.md`, beside this file; cite them by section number so the author can check you. **Read before reporting:** guide §13.2, the stage rubrics. Every check there carries a *test*, the *cost* if it fails, and a *suggestion*, and the cost is what separates a finding from a preference. Read the rest of the guide by section as findings need it — §13.2 cites the underlying rule by number, and the guide's Contents table maps every number to a heading. Do not read the guide end to end — it is long, and a review that stops at one stage needs two or three of its sections. **Locating the guide and the checker.** Both live beside this file, in the skill's own directory: ``` references/ERC_writing_guide.md the rules tools/erc_check.py stages 8 and 9 ``` The draft is in the working directory, which is *not* the skill directory. Set `ERC` to the directory holding this file before running anything; if you do not have that path, find it: ```bash ERC=$(dirname "$(find ~/.claude -name erc_check.py -path '*erc-review*' 2>/dev/null | head -1)")/.. ``` Then `$ERC/tools/erc_check.py` and `$ERC/references/ERC_writing_guide.md` work from anywhere. Run the checker *from the draft directory* — it resolves `b1.tex` and `b