Scrutinize (dispatch)

Stand outside the change and ask whether it should exist at all, then verify it actually does what it claims — within the blast radius of the task you were given.

This is scrutinize retuned for one caller: a reviewer subagent that was dispatched, cannot ask the author questions, and whose report a controller parses for exact words. It differs from scrutinize in five places — scope, severity vocabulary, the cannot-verify channel, the verdicts, and a set of dispatch-only operating rules (no subagents, do not trust the implementer's report, read-only) that scrutinize has no need of since it runs in a live session with a human at the keyboard (ADR 0084). One check is deliberately dropped rather than retuned: the UI-mock diff, since a diff-scoped reviewer has no way to fetch a mock.

Operating stance