Verify a decision

{"actor":"judge","decided_at":"2026-08-25T22:19:40.888Z","decision":"review_revise","investigation_id":"f7b62b47-2118-46e9-8025-4f381f47211f","new_score":0,"page_slug":"q2-2026-record-crypto-hack-wave","prev_score":0,"reason":"Of 34 claims checked, 24 were confirmed outright and the page's central numbers -- the 83-incident/$755.3M quarterly total, the KelpDAO and Drift Protocol loss figures and attack mechanics, the THORChain and Humanity Protocol incidents, bridge-loss aggregates, and the year-by-year rise in North Korea's share of hack losses -- held up against independent sources. Using the disputed+unverifiable share of total claims (excluding partially_supported and link_rot, per spec), disputed_pct is 6/34 (17.6%), placing this page in the minor-issues band. The substantive defect is a real one: the page's own cited source, TRM Labs, ties only the KelpDAO breach to the TraderTraitor subunit and describes the Drift Protocol attacker as a distinct North Korean group still under investigation, while the page's summary and its dedicated attribution section merge both into a single TraderTraitor/UNC4736 claim (claim_findings[2], claim_findings[26]) -- the same underlying error surfaced twice rather than two independent mistakes. A citation for the March 2026 OFAC action instead resolves to an unrelated 2019 Treasury release (claim_findings[29]); the underlying fact is independently confirmed elsewhere, so this is a sourcing defect rather than a false claim. The four unverifiable findings (claim_findings[9], [11], [16], [28]) are peripheral details -- a forensic detail, a fund-relocation figure, a historical ranking, and precise cumulative-loss figures -- that the reviewer could not locate corroboration for in the time available rather than claims shown to be false. No coverage gap was rated high priority, and reviewer confidence (0.75) supports a moderate rather than severe penalty.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}