Verify a decision

{"actor":"judge","decided_at":"2026-08-25T03:44:12.939Z","decision":"review_revise","investigation_id":"fa3e4739-2493-471f-b16a-4a0503f66079","new_score":13,"page_slug":"coinkite-coldcard","prev_score":18,"reason":"This page's central factual narrative -- the RNG root cause, entropy collapse figures, affected firmware ranges, attack-wave amounts, the prior-warning account, and the CTO pseudonym allegation -- is confirmed by the review against independent primary reporting and is appropriately hedged where facts remain allegations rather than proven conclusions (claim_findings[3-9], [15-16]). The disputed_pct sits exactly at the 10% boundary (25 confirmed, 2 partially supported, 1 disputed, 2 unverifiable out of 30, reviewer confidence 0.8). I place this on the revise side of that boundary for two reasons that are independent of raw percentage. First, claim_findings[28] (the sole 'disputed' item) shows a quote attributed in quotation marks to Kraken's CSO in the Industry Impact section that does not match his verified wording and traces to a source not even cited in that section -- a real citation-integrity problem, even though it concerns a third-party commentator rather than the page's subject. Second, the review's own coverage_gaps flag two high-priority gaps (Coinkite's own technical post-mortem is not yet cited, and the CTO-identity GPG signature claim has not been independently replicated by any outside researcher) -- per standing review policy, high-priority gaps push a borderline page toward revise even when disputed_pct is low. Claim_findings[11] additionally shows the page's own summary attributing an 'in crypto history' superlative to TRM Labs when TRM's source language is scoped only to 2026, a sourcing overstatement in a prominent location. None of these issues touch the page's core allegations against Coinkite or its CTO, which remain solidly supported and properly hedged, so the penalty is set at the low end of the revise band.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}