Verify a decision

{"actor":"judge","decided_at":"2026-08-26T08:08:38.532Z","decision":"review_revise","investigation_id":"ef51aa99-9639-4d3d-a2cb-0e03d1142485","new_score":8,"page_slug":"taiko-l2-bridge-exploit-june-2026","prev_score":22,"reason":"An independent fact-check of this page found the core story to hold up: the $1.7 million loss, the leaked SGX signing key as root cause, the attack mechanics, and the placement of fault on Taiko's own operational security rather than a third-party provider are all well corroborated across independent sources, with zero of 34 checked claims actually disputed (claim_findings[0], [7], [10], [12]). The page falls short in one consequential way: its restart-plan section ends at a June 28, 2026 snapshot stating recovery pull request #21820 remained unmerged (claim_findings[23]), while multiple independent outlets confirm the bridge fully reopened, was recollateralized 1:1, and all roughly 4,500 affected users were made whole within about two weeks -- none of which the page reflects despite being reviewed nearly two months later. As published, this leaves readers with the false impression that the incident and user compensation are still unresolved. A dead citation pair on the exchange-suspension claim (claim_findings[18]) and a citation-trail gap on an attributed claim (claim_findings[26]) compound the currency problem but do not touch the substance of what happened or who is responsible. This page needs a prompt update to its resolution status, not a re-investigation of the underlying allegations, which remain solidly supported.","score_delta":-14,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}