How verification works
Every pool lead earns points from public records and imagery. The score is the sum of those points — weights live in config so operators can tune them without a redeploy.
Points per evidence source
| Source | Points |
|---|---|
| Aerial / model detection | +1 |
| Assessor record indicates a pool | +1 |
| Human rejected (not a pool) | -5 |
| Human verified pool | +5 |
| Licensed data flag | +1 |
| Multi-vintage agreement (covered pools) | +1 |
| Visual imagery check | +0.5 |
Badges
| Badge | Requirement |
|---|---|
| ★ Certified | score ≥ 5 + human event |
| Probable | score ≥ 1 |
| Verified | score ≥ 2 |
Score is the sum of event points from config. Badges: Probable / Verified / Certified (Certified also needs a human event). Weights live in admin config, not code constants (R4).