A Review Map is a review agenda: the smallest set of judgments a change asks
of you, each with the code that settles it attached. These two were produced by
accountable-review against open
pull requests in public Rails codebases, so every file:line citation on them
resolves — you can follow any claim straight into the repository it is about.
They are ordinary output, not showcases: no page was edited after the run produced it.
Eleven files that all look safe: a new table, the callbacks that keep it in step with the live one, and a backfill task. What a reviewer has to judge is in code the diff never opened: every path that starts or ends an ownership has to keep the one history row in step with it, including paths that never run the callbacks.
Open the mapA medium change across the signup path, and the one that shows what the format is for: most of what a reviewer has to decide lives in code the diff never opened. The change moves which request creates the account, and a reader new to Discourse has to see that move before being asked whether every such request still passes the CAPTCHA.
Open the map
Generated on 2026-10-19 with accountable-review 1.3.0, at --effort high and --mentor off.
The page format moves between releases, and every release regenerates these, so the version is
recorded rather than implied. Provenance for each page.
A Review Map is a pass over a change, not an audit of it, and it carries no verdict on either pull request — see what a Review Map cannot do.