Verify a decision

{"actor":"judge","decided_at":"2026-08-26T15:13:38.251Z","decision":"review_revise","investigation_id":"5f3c2907-8e30-4d82-a4a7-875cd9bc7d2c","new_score":24,"page_slug":"hyperbridge-polkadot-ethereum-bridge-april-2026-exploit","prev_score":32,"reason":"I checked the reviewer's arithmetic: 26 confirmed, 7 partially_supported, 1 disputed, 2 unverifiable, 0 stale, 0 link_rot across 36 claims gives disputed_pct = (1+2)/36 = 8.3%, matching the reviewer's own figure and the reviewer.md formula (partially_supported excluded from the numerator). On the raw table this sits inside the 0-10% approve band, and the page's central facts hold up well: the exploit date, target, root cause, and the loss revision from $237,000 to $2.5 million were all confirmed by directly fetching Hyperbridge's own post-mortem (claim_findings[1], [3], [7], [15]). I am escalating one band anyway, on a single named mechanism: coverage_gaps[0] (priority: high) is not an ordinary expansion suggestion but a structural omission directly tied to claim_findings[27] — Hyperbridge's own April 23, 2026 'First Returns' post documents a partial voluntary fund recovery that the page's Recovery Efforts section omits entirely, leaving that section reading as more unresolved than the record supports. That, combined with a compounding misattribution to named security firms (claim_findings[9]: CertiK is credited with confirming mechanics it only confirmed occurred, and 'Blocksec Falcon' appears to be a garbled, superseded-theory rendering of BlockSec Phalcon) in a section the page marks critical severity, is enough to warrant a light, unbannered-status revision rather than a bare approval. None of the remaining partially_supported findings (slug simplification, bio citation mismatches, Hypernative mischaracterization, Q1 figure sourcing) rise to the level of factual inaccuracy — they are citation-hygiene and precision issues on facts independently verified as true.","score_delta":-8,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}