Read a review

Read the assessment for each environment before acting on its findings. A review records the code and evidence used for that assessment.

Check the change#

Open the review from Reviews or its pull request. Confirm the repository, commit, and environment match the change you are investigating.

A queued or running review may not have assessments yet. Wait for the result before treating the findings list as complete.

Read the assessment#

Each environment has its own context. A result for one environment does not establish the result for another.

An incomplete assessment means Proofline could not finish with the required evidence. Inspect the reported reason and the environment's evidence coverage.

No supported findings is not a guarantee that the deployment is safe. Missing, stale, or unavailable evidence remains a limitation of the assessment.

Follow a finding#

Open a finding to read what can fail, why the change causes it, and which evidence supports the explanation. Compare the suggested correction with your intended behavior.

Use Read and act on a finding for the next steps. If the code or environment changes, run a new review rather than treating the old result as current.