What a finding says

A review leads with a verdict, then lists what it found. Every finding says how we know it, and “not verified” is an honest answer.

How we know

Mark	Means
We ran it	The old and the new code ran the same input, or the test ran.
We traced it	Read straight from the code.
We proved it	A proof that replays.
We could not	Not verified. We say why, and what would let us.

A finding a test or a scenario showed happening is marked Verified: the test or scenario the review wrote failed on the change and passed without it, and a check found that it tests the finding the way real callers would. The run is attached.

A finding

Each finding carries:

• Its severity, from critical to info.
• Verified, when a run showed it.
• Where it came from: a rule over the graph of what changed and what it reaches (graph), a test that behaved differently on the new code (simulation), the review agent reading the graph and the code (agent), or a scenario the review wrote and ran on both sides of the change (scenario).
• How many of the review agent’s runs raised it, such as 3/3 runs, when it ran more than once. One raised by a single run shows quieter.
• Where it breaks: in the change, after merge in code the change did not touch, or far from the change.
• How sure the reviewer is, as a percentage.
• How it breaks: the input or call, and the wrong result, in one sentence.
• The evidence, the other places involved, and a suggested fix when there is one.

The comment on the pull request carries the findings a maintainer should read before merging; the full review on graphide.com has every finding.

The verdict

The review’s verdict is also its Graphide review check on GitHub:

Verdict	Means
Merge	Nothing found that needs a look first.
Look first	Read the change first: neither pass nor fail.
Hold	A finding the review posts should hold the merge.
Not reviewed	The review could not judge the change.

Tests the review did not run (too long for its test window, unfinished, no runner for them) are named in the check’s summary; your CI still runs them. Whether a verdict can hold a merge is up to you: Merging and required checks.