verify-claims

Verify a code change by converting the claim into concrete evidence: run the relevant test or command, record its output, note which code paths it exercised, and assign a confidence level. A passing command only proves what it actually covered.

Document a review finding by capturing four elements: the claim itself, the evidence such as a file path or command output, the scope of what the evidence covers, and a confidence rating of high, medium, or low with the reason.

A passing test is not proof beyond what it exercised. It only validates the specific scenarios and code paths it ran, so you should record the scope of coverage and assign an appropriate confidence level rather than assuming full correctness.

Use claim verification before asserting that a change, diagnosis, plan, or test result is correct. It is emitted as evidence for later work rather than acting as a blocking stage or prerequisite in your process.

Evidence-based verification is limited by the freshness and locality of evidence and by what the evidence actually covers. Stale or indirect observations lower confidence, and no single command output can prove claims outside its exercised scope.