Reach

A change that reaches further than its kind assumes should be re-classified, so an anchor run measures the diff and asks. Only quick and inline loops are measured, since they run no review.

What is counted, the thresholds, and what verify waits for

An anchor run or declared verify of a quick or inline loop measures the diff’s reach: source files (not tests, lockfiles, specs, or prose), the top-level directories they sit in, and a README, changelog, or *.schema.json changed beside them. Files already changed when a repo joined the loop count only once their content changes, and a file at a repository root counts as a file, not a directory.

At 3 source files, 2 directories, or one such file, the result carries one line asking to re-classify. verify then waits for a kind call with a reason that answers each threshold crossed, and a later threshold asks again.