How Three Unchecked Non-Figure Claims Exposed Gaps in a Code Review Checklist

A software development team discovered that a commit receipt contained three factually incorrect claims — about a carrier label, a sequence position, and a branch state — even though every numerical figure in it was accurate. The errors went undetected because the team's verification rule only required reading back figures and text, not every type of claim a receipt could make. The rule was subsequently broadened to require read-back verification of all claims, including coordinates, states, and counts, not just numeric values. A separate checklist item was also found to be ambiguous, as it failed to specify which file set a link-checking tool should scan, allowing a branch to pass locally while risking failures in the repository's shared cycle. These findings highlight that verbatim text verification against a source does not guarantee the accuracy of the claims that text makes.