Verify a decision

{"actor":"judge","decided_at":"2026-08-25T14:05:24.679Z","decision":"review_revise","investigation_id":"e620d5be-6208-44a1-89e0-67163f0f5c08","new_score":0,"page_slug":"ascendex-insolvency-and-withdrawal-freeze-july-2026","prev_score":2,"reason":"The page's core insolvency narrative is well supported: the reviewer independently confirmed the shutdown date and stated reasons, the $240M reserve drop, the $13.45M on-chain figure and its ASD/UNITE composition, the withdrawal-freeze mechanics, and the 2021 hack's dollar figures against primary and tier-1/tier-2 sources, and the page carefully distinguishes a withdrawal pause from a liquidity shortfall from a hedged insolvency warning without ever overstating that formal insolvency has been declared (claim_findings[6], [24], [25]). At 7.7% disputed, the raw ratio sits inside the approve band, but two disputed claims carry outsized weight and both also surface as high-priority coverage gaps. First, claim_findings[20] attributes the December 2021 hack to the Lazarus Group, a specific named state-linked threat actor, but neither of the page's own two cited sources mentions this, and a dedicated incident-tracking database states the attacker was never identified -- naming a specific perpetrator where the honest answer is 'unknown' is a serious, unsupported claim. Second, claim_findings[14], in the section on the failed strategic transaction that is central to the insolvency story, says the counterparty was undisclosed as of the investigation date, when AscendEX had apparently already named it (RIBK) in an official statement carried by a source the page cites elsewhere -- asserting concealment where disclosure had occurred is an unfair characterization of a distressed company, though the reviewer notes some uncertainty about whether that disclosure predates the page's investigation date. A third, non-disputed but flagged issue (claim_findings[16]) has the page's MiCA framing invert its own cited source, implying AscendEX's non-authorization signals unique dysfunction when the source shows most industry peers also failed to clear the bar. Together these are two specific unsupported/inverted claims that push blame or suspicion onto named parties without adequate sourcing, warranting a revision request rather than approval, but the strength of the remainder of the page and decent reviewer confidence (0.78) keep this in the low end of the revise band.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}