Verify a decision

{"actor":"judge","decided_at":"2026-08-25T03:01:13.535Z","decision":"review_revise","investigation_id":"1e2462e5-693f-4f90-81f9-451e466d3552","new_score":0,"page_slug":"cyberleek-token","prev_score":8,"reason":"Of 50 claims checked, 44 were confirmed and none were disputed, so the review's disputed_pct of 4% would normally support a clean approval and the page's core narrative — pre-built token infrastructure preceding the alleged leak, the DMCA subpoena campaign, and the wallet-cluster analysis — holds up well (claim_findings[0-8], [20-33]). However, one stale finding sits on a load-bearing, 'critical'-severity claim: the page presents an operator wallet as currently holding 270 million CYBERLEEK tokens, but the page's own cited KuCoin source reports those tokens were burned around Aug 22, 2026 — before the page's own Aug 23 'as of' date (claim_findings[24]). That is compounded by two high-priority coverage gaps the review identified: the omission of Stop Killing Games' public disavowal of the campaign, and the omission of the Aug 22 burn event from the page's timeline, which is the same fact underlying the stale wallet claim. Per the review criteria, high-priority coverage gaps push toward revision even when disputed_pct is low, and a stale claim on a critical citation adds further weight toward a penalty. The two unverifiable findings stem from HTTP 403 fetch blocks on BeInCrypto and the Bitcoin Foundation rather than any indication the underlying claims are wrong, so they were weighed leniently and did not add to the penalty. Given the reviewer's reasonably high confidence (0.78) and the narrow, correctable nature of the problems, a modest downward adjustment with a revision request is warranted rather than approval or denial.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}