Verify a decision

{"actor":"judge","decided_at":"2026-08-27T11:04:49.086Z","decision":"review_revise","investigation_id":"ccd5c96d-c9d5-49cc-b59d-3dab935b8d49","new_score":37,"page_slug":"panoptic-v11","prev_score":45,"reason":"Of 22 checkable claims, none were disputed and only 2 were unverifiable, putting the raw disputed rate at 9.1% -- just under the approve threshold -- and the page's core narrative about the August 2025 position-spoofing incident, its cause, the whitehat rescue, and the bug bounty is confirmed in precise detail against primary sources (claim_findings[2], [4], [16]-[20]). However, all seven of the page's content sections are empty and its source list is unused, so the page's structure promises analysis (protocol background, team, audit history) it does not actually contain; this is logged as a high-priority coverage gap (coverage_gaps[0]) that, under our rules, pushes the outcome to a revise even though the disputed rate alone would clear the approve bar. Two smaller issues reinforce a cautious rather than punitive revise: the summary's '$4-5 million at risk' figure overstates both the primary source and the page's own timeline math (claim_findings[3]), and an unverifiable claim attributes commentary to ZachXBT that no source, including Panoptic's own post-mortem, corroborates (claim_findings[5]). Several dates also use an imprecise first-of-month placeholder pattern (claim_findings[8], [9]), a minor but recurring accuracy issue.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}