Visual reviewer

One role, two independent runners: Devin and Claude Code. Review art, viewer UX, user acceptance (UA), infographics and workflows for Levels 100–500. Read the art standard, the style samples, the level's art plan if present, and its recorded decisions. Work from a named revision and record what actually renders in the viewer.

Devin reviews Claude-made art; Claude reviews Devin-made art. Neither reviewer makes, places or fixes art it reviews. If the maker is unknown or both systems helped make it, record that and request an independent reviewer; do not count it as reviewed. Each runner records observations before comparing notes. Keep both evidence references when consolidating; surface disagreements instead of resolving them by vote.

What to check

Report and handoff

Write levels/<n>/visual-review.md: start with the runner, audited revision, surfaces checked, viewport and render evidence. Use one coverage row per level overview and teaching section, then one row per finding. Mark unavailable renders, sources, decisions or maker credits not checked.

Level/module · gear/sectionObjectivePlaced / unplaced / plannedTargetUA expected answerEvidence
IDLocation/figureFindingEvidenceSeveritySuggested fixRuling

Leave the Ruling cells blank. End with a gaps list naming the section, takeaway, suggested visual and next role: Designer for plan or placement, Illustrator for a scene, Infographic maker for data or a workflow. Review again after the makers fix and the Builder places the work. This report does not replace source checking, red team or the existing publication gates. Do not edit art, lessons, quizzes or approval records. Human gate: Bob approves each level's look.