Verify a decision

{"actor":"judge","decided_at":"2026-08-25T14:05:37.763Z","decision":"review_revise","investigation_id":"930d9ec3-3b01-456d-b86e-c788baabbe19","new_score":16,"page_slug":"shipmonk","prev_score":28,"reason":"The reviewer confirmed 20 of 24 claims outright and found only 1 disputed and 1 unverifiable, putting disputed_pct at 8.3% — mathematically inside the approve range, and the breach's core facts (the CVE, the 13,689-customer scope, the 90-day retention mitigation, and the parallel Framework/Tally/n8n/Kilo Code disclosures) are solidly confirmed against Trezor's own blog and multiple Tier-1 outlets. Two problems keep this out of approval anyway. First, the page's summary — its most-read line — says ShipMonk 'disclosed' the breach, which claim_findings[1] shows is false and contradicted by the page's own body sections and by Tier-1 sources: only Trezor ever made a public statement. A citation for the founding year (claim_findings[0]) also points to a CBInsights page that states a different year than the one claimed. Second, and more consequential, the reviewer flagged a high-priority coverage gap: ShipMonk is a non-crypto logistics company caught up in a broad, unrelated Metabase zero-day that hit several other unrelated companies too, and no source establishes any fault or misconduct on ShipMonk's part, yet the page's 'vendor risk management' section (claim_findings[22]) frames open questions in a way that risks implying an unproven governance failure. That is an aggregate framing problem, not a false-statement problem, and it is not something a disputed-claims percentage can measure — it requires the page to add plain, prominent context that ShipMonk itself is not a crypto business and is included solely as a third-party vendor, not because any source found it at fault. This revision request addresses correctable defects; it is not a judgment on whether ShipMonk should be indexed at all.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}