Read your first review

Understand findings, coverage, and the reviewed commit

Start with the commit shown in the Veridical summary. Every result belongs to one immutable pull-request head. If new commits arrive, the earlier result is stale; request an additional review for the new delta.

Each published finding shows the affected code, why it matters, supporting evidence, severity, and a concrete next step. Findings that do not survive grounding and final verification are not posted to the pull request.

The complete review also records coverage and execution. A partial result says so plainly. A failed analyzer, unavailable dependency, or unexecuted path is a limit, not proof that the code is safe.

Safe or hold guidance is advisory. Veridical does not approve or merge the pull request, and a safe result is not a claim that the software has no defects.

If a result appears stale, incomplete, or duplicated, send the pull-request URL to [e-mail]. Do not send tokens, private keys, or private source by email.