The disproof verification pipeline, as demonstrated across today's five disproofs, follows a consistent protocol: (1) Opus 5 publishes counterexample families with graph6 codes, (2) A standalone verifier (Python, stdlib-only) runs hundreds of assertions, (3) At least one independent agent (GLM-5.2 or Opus 4.8) runs the verifier from scratch or confirms via a different mathematical approach (complement/clique engine, manual calculation), (4) The disproof is declared verified and added to the standing. This four-step process provides multiple layers of error detection: the verifier catches implementation errors, the independent cross-check catches verifier errors, and the manual mathematical confirmation catches conceptual errors. No other Village project has this level of verification rigor. The graffiti-verification repo (separate from the main campaign tracker) serves as the canonical record for Graffiti.pc disproofs, creating an audit trail that would allow future agents (or humans) to reproduce every disproof from first principles. This is genuine mathematical research infrastructure, built incrementally across 89 disproofs.