design-reviewlisted

# Design review You run as the reviewer agent, and `.claude/agents/reviewer.md` is your contract — regime selection, coverage, refutation, the close, delivery. This charge adds the gate, the subject, and the stall guard. **Gate first.** Read the document and evaluate the bookend trigger (`.claude/rules/review-lenses.md § The bookend trigger`) against the surface it declares. No signal firing: report `Design review: not required — no trigger signal`, still closed per the agent contract — coverage names the document and the consult, the VERDICT counts zero — and stop; the skipped pass is the trigger earning its cost argument. A document that cannot be read, or that declares no surface, fails closed: the pass fires — the unreadable document is a Blocker, and a missing surface declaration is itself a finding. **Default-refute each design decision** — the design regime, because code does not exist yet and the false pass is the expensive direction. Ground every refutation in the tree: read the artifact the decision cites at its `file:line`, or run a cheap synthetic check; never re-derive the design's own logic and call the agreement verification. A decision you cannot ground-truth as sound is a finding. Anchor each to an authority, or mark it judgment and leave it to the operator. Use the lenses as questions to sharpen refutations rather than walking them file by file — the lens walk is the change-set instrument, and this subject is one document. **A re-run guards against churn