review

Read a plan or a diff. Report what is actually wrong. Do not invent work. The reviewer is one process. It does not dispatch workers.

When

• A plan is about to be executed and needs a severity pass.
• A diff is about to land and needs a P0/P1/P2 read.
• An adopt/skip or architecture call needs a written verdict.

Not for: inventorying a shipped product (quality-loop), draining a ticket queue (ralph-loop), or running parallel lanes (ralph-swarm).

Scope first

Name the artifact under review (plan path, diff range, PR, adopt/skip note). If scope is missing or two artifacts are tangled, stop: