Verify a decision

{"actor":"judge","decided_at":"2026-08-26T16:06:11.109Z","decision":"review_revise","investigation_id":"d9ede437-ae38-4d5f-b563-ac48f657c4d5","new_score":9,"page_slug":"bitmart-exchange-shutdown-2026","prev_score":22,"reason":"The page's core narrative -- that BitMart announced a wind-down on July 26, 2026, halted trading on August 26 as scheduled, saw its BMX token collapse, faced withdrawal delays, and previously suffered a $196M hack in 2021 -- is well-corroborated and the review found no conflation of the 2021 hack with the 2026 events (claim_findings[18], overall_assessment). Disputed_pct lands at 12.9%, squarely in the minor-issues band. Two things push the penalty toward the upper end of that band rather than the low end: the page states BitMart's full closure by January 31, 2027 as settled fact, but BitMart itself announced on August 21-22, 2026 -- before this review -- that it may pursue a restructuring with partial resumption and creditor payouts instead (claim_findings[1], reinforced by coverage_gaps[0] and coverage_gaps[1], both flagged high priority); and the page states BitMart 'lost' UK regulatory authorization in October 2023, when the FCA's own record shows BitMart never held that authorization and the actual FCA actions were standard unauthorized-firm warnings issued later, in September 2024 and July 2025 (claim_findings[22]). A separate misattribution -- crediting CoinDesk with 'over 30' failed crypto projects in 2026 when CoinDesk's own reporting cites 63 and later 100+ -- understates rather than inflates the industry-decline narrative and is a lower-severity sourcing error (claim_findings[27]). One remediation-related gap works in the subject's favor: the page omits that BitMart's 2021 reimbursement pledge left some token holders, notably SAFEMOON holders, unpaid for at least a month (claim_findings[19]), meaning the page is arguably too generous on that point.","score_delta":-13,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}