Verify a decision

{"actor":"judge","decided_at":"2026-08-25T13:56:05.299Z","decision":"review_revise","investigation_id":"545f775d-f1a1-4fc5-9939-be733ad3dcc5","new_score":0,"page_slug":"bitradex","prev_score":4,"reason":"The page's regulatory core holds up: all four regulator actions cited (Thailand SEC, Securities Commission Malaysia, Alberta Securities Commission, and the separate 2022 FCA notice) were confirmed against primary or verified secondary sources with correct dates, and the page properly distinguishes regulator warnings from adjudicated fraud. But two sourcing problems and one material omission mean the page needs correction before standing as approved. claim_findings[30] found that the page's claim of a BitradeX listing in IOSCO's I-SCAN database cites a specific source page that does not mention IOSCO or I-SCAN anywhere -- a fabricated attribution in a section the page itself marks as critical severity, though the page does separately flag that specific line as 'not independently verified,' which limits the practical damage. claim_findings[5] found that the page's summary -- its most-read, least-hedged text -- states as near-fact that BitradeX has 'Chinese-origin ownership obscured behind a UK-registered shell,' while the body correctly frames this as unconfirmed circumstantial indicators layered over a confirmed Indian-national controller; the most visible line on the page overstates what the evidence underneath it actually shows, on a claim about national origin. Separately, the review surfaced a high-priority gap: a $14M+ BitradeX Capital/BXC token fundraising campaign running April-May 2026, concurrent with the regulatory warnings, that goes entirely unmentioned despite bearing directly on the page's core thesis about capital solicitation from an unregistered platform. Taken alone, the raw disputed rate (1 disputed and 1 unverifiable claim out of 43, about 4.7%) would support approval, but a fabricated citation and a summary that outruns its own body on a sensitive ownership claim are integrity issues a claim-count percentage cannot fully capture, and a high-priority coverage gap on point to the page's central allegation independently warrants revision under this process's own rules.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}