Review the evidence first
Judge the outcome from its evidence before you read the code. An approved outcome stays approved when the code is fixed and the checks pass again.
At Blume, we review in two steps. First: does the change do what was asked? That is the outcome review, answered from evidence. Second: is this code we want in the codebase? That is the merge review, answered from the pull request.
What goes wrong when code comes first
Code first
An agent opens a pull request: 900 changed lines for a new onboarding screen. You read the diff for forty minutes, leave six comments and approve.
Then you open the app. The screen asks for the team name before the person has chosen a plan. That was visible in ten seconds, and the 900 lines are rewritten.
Evidence first
The agent asks for the outcome review. You see the flow as screenshots at the commit under review, and each acceptance check with its evidence.
In two minutes you write: “Plan first, then team name.” The next revision shows the flow you wanted. You approve the outcome, and only then read the code.
What to do
- Start from the checks. Is each check’s evidence the right kind, and did it pass at this revision?
- Answer in words when it is a no. That sentence becomes the agent’s next piece of work.
- Do not read the diff yet. Review the code when the pull request is ready to merge.
An approved outcome carries over. If the merge review asks for a code change and every acceptance check passes again, your outcome approval carries to the new revision.
In Blume
- The outcome review opens on the agent’s presentation, with the evidence each part cites.
- The merge review is asked once the pull request is ready to merge.
- A revision that kept an earlier approval is shown as “Outcome carried”. See reviews.