Sofia/DB-cleanup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Activity
Files
93cf7ae53ae219eb6a9eb88695b3ee1b5860d67d
DB-cleanup/merge-output/sofia-worklist.md
T

26 KiB
Raw Blame History

Sofia — manual source worklist

Every source the automated pipeline could not retrieve. Open each in your browser, copy the article text, and paste it back to me with the case number. I file it verbatim.

Ordered by urgency: the cases at the top have NO other working source — losing them means the case has zero evidence. Cases lower down already have other articles on file, so their missing source is a nice-to-have, not a gap.

Verdict meaning: DEAD = link 404/gone (try the Wayback Machine). THIN = the page needs a browser to render (JavaScript). BLOCKED = the site refused an automated request but will open normally for you.

NO OTHER SOURCE — priority

has 1 other source(s)

has 2 other source(s)

has 3 other source(s)

has 4 other source(s)

Special: La Provence, paywalled (serves cases 457 AND 458)

We hold only the opening 25%. The rest is behind the paywall and unreachable by any tool. If you can read the full article, paste it and I'll file it into both case files. The missing portion likely contains the Gignac-la-Nerthe detail (458) and any answer on the plate question. https://www.laprovence.com/article/faits-divers-justice/2193885092828214/quatre-hommes-arretes-en-plein-braquage-sur-fond-de-cryptomonnaies-pres-de-marseille

  • Case 391 (Chinese national rescue, 2 arrested) — its only linked source (abs-cbn.com) is JS-rendered and returned no article body. Needs a manual/browser fetch or a replacement source. No usable article on file otherwise.

Cases with no article text — fresh search 2026-09-06

Seven of the ten were found by web search and filed as extra sources (marked "NOT on the DB record" in the dossier; add the URLs to the record if you agree): 258 Kharkiv (Ukrinform, Hromadske Radio, Sud.ua, ATN — also gives the victim's age 32, a Mercedes Vito, 14,600 EUR cash taken first, and one active serviceman among the three), 260 Nate Geier (Mothership), 358 Bangkok (Khaosod English — victim attacked 1 November on Mahaseth Road, not 10 November; the DB date is the first arrest), 365 Las Vegas (The Defiant; 8 News Now is the original but blocks fetches — it is already the source on case 323, the duplicate record), 388 Verneuil-sur-Seine (Actu17, Mantes Actu), 390 Zoersel (VRT NWS, NNieuws, In de Gazette — VRT says two intruders, firearm, facial injuries, Korte Maalstraat, 10 January), 430 Homestead (Decrypt, Fortune; the DOJ press release is the primary source but fetches as an empty shell — copy it by hand from justice.gov/usao-mdnc, "Twelve Defendants Sentenced ... Cryptocurrency"). Still nothing on file for three cases:

  • case 11 (Josoj, London 2017): the only source is a podcast episode (ivoox, Bitcoin Uncensored). No text article exists that I could find. Options: transcribe the episode (would be a derived text, label it so), or link the LocalBitcoins forum thread where the victim posted, if you know it.
  • case 66 (East Lansdowne BTM, May 2020): the only source is the East Lansdowne Police Facebook video. Search Delaware County local press (Delco Times, 6abc, NBC10) for "bitcoin ATM" "East Lansdowne" May 2020, or ask the police department for the incident number.
  • case 399 (Dominican Republic, Oct 2025): reported directly to Gart Research by the victim; there is no public source. File the victim's own account as the source, labelled as a first-person report.

Round-up articles needing per-case passage isolation (Claude to do, your review)

One article covers several different cases; each case file must keep only its own passage.

  • Known set: 68, 315, 422, 445, 450.
  • 375 (Trincity, Trinidad) — its cryptonews article bundles several separate Trinidad incidents (a St. Joseph car theft at para 17 is a different victim) then goes global. Left UNTRIMMED pending isolation.
  • Newly found: 423 and 424 — both link the SAME San Francisco Chronicle article (byte-identical), a multi-victim wrench-attack round-up. Left UNTRIMMED pending isolation so the two files don't cross-contaminate.

Wrong-source / mismatched cases (the linked article does not describe this record)

  • Case 248 — the linked leparisien.fr article is a DIFFERENT incident (a woman assaulted at home in Suresnes, France), NOT the Oslo Norwegian-family home invasion this record describes. That Suresnes event is case 242, which already has a BFMTV source — move the Le Parisien URL to 242. UPDATE 2026-09-05: Oslo sources found by web search and filed into 248 (marked "NOT on the DB record" in the dossier): Document.no 09.08.2025 (the detailed account: Haugerud, Foodora disguise, parents in their 40s, children 4/8/12 taped up, mother threatened with being shot, crypto demanded, four men from Sweden aged 18-22), Avisa Oslo 06.08.2025 (police statement, incident reported 23:53 on Tuesday 5 August), NRK 30.08.2025 (nine charged, one man in his late 20s remanded four weeks, straw men rented a hideout flat), Document.no 04.09.2025 (nine charged for aggravated robbery and deprivation of liberty, three adults and two minors bound, one threatened with a firearm, one subjected to serious violence, two arrested abroad on international warrants). Decisions for you: (a) add these URLs to the record; (b) date = August 6 but police log the call at 23:53 on 5 August — pick one and say "night of 5-6 August"; (c) the record's "Ledger wallet" search and "handler / third-party DB leak" notes do not appear in any Oslo source found — the handler detail is a Suresnes fact and probably leaked in from the wrong article; Document.no instead says police suspect the job was ordered by people close to the family. Confirm or drop; (d) Document.no says three adults were bound per police, while the record says a family with three children — the police count (3 adults + 2 minors) and Document's (2 parents + 3 children) disagree; keep both with attribution.
  • Case 441 — its fetched sources (url_2, url_3) actually describe case 438 (same Montreal home-invasion cluster, wrong incident). Decide: drop them, or move to 438.
  • Case 295 — the Forbes source (url_3) predates the event it is filed under, so it cannot be reporting on it. Decide: drop or replace.
  • Case 358 — the DB url points to an unrelated thethaiger dog-in-floods story, not the Bangkok kidnapping. Correct the URL and find the real source (also in the source-gap list — it is sourceless).

Probable duplicate record

  • Case 323 ≡ Case 365 — almost certainly the same incident: three teenagers, a crypto-event host kidnapped at gunpoint on the way home, driven to a remote desert (~1 hr out, White Hills AZ), ~$4M in crypto + NFTs, released in the desert, victim walked ~5 miles to a gas station, a 4th person on speakerphone. 323 (8News, court records) names the charged teens (Belal Ashraf, Austin Fletcher, both 16, Pasco County FL) and puts the event in Downtown Las Vegas — so 365's notes "Downtown LA" is a typo. Decide whether to merge 365 into 323. (365's summary drops the city to avoid asserting the error.)

DB record / flag corrections (surfaced while writing summaries — apply on the website)

Authoritative correction lists already exist: corrections-register.json (35 fixes, with status) and corrections-for-database.json (per-record: id 321 victim, id 307 description, id 258 archive link, id 460 name/ownership/amount/scene-list/weapons, id 462 weapons note, sheet row 18 scenario, sheet row 252 wrong URL / Phuket case). Additional items found during the summary pass:

  • Case 67 (Ellis Pinsky, Irvington NY, May 2020) — description says "2 men commit home invasion of hacker"; the Daily Voice source only reports an indictment for conspiracy to commit the robbery, and the owner confirms the plan was foiled. Reword to "planned home invasion, foiled; two indicted for conspiracy". Flags stay 0.
  • Case 334 — bulk summary said "Victim deceased"; WRONG. The victim (unnamed São Paulo businessman) survived (thrown from the car, 3 fractured ribs, rescued by a truck driver); life_taken = 2 is two SUSPECTS killed by police. Also clarify whether life_taken counts perpetrator deaths (your earlier rule was "counts victims", under which 2 would be wrong here).
  • Case 353 — money_wanted "100 million rubles" is misattributed (that figure is an unrelated Irkutsk case in the same article's tail); this robbery took 100 GPUs / 4 containers, damage only "could significantly exceed 1 million" (currency unspecified).
  • Case 301 — bulk summary "180 BTC" was wrong: it was 180 bitcoin mining MACHINES (ASICs).
  • Case 299 — money_wanted lists the four amounts as "Euros"; the Guardian source says POUNDS (£).
  • Case 290 — description says "$100,000" but the sums taken were Dhs300,000 + Dhs63,000.
  • Case 298 — description says "$1,000,000" while money_wanted/source say Dh4.12m.
  • Case 219 — description "beaten with a stick" contradicts the article (bag simply snatched from behind, no violence); the flags (violence/weapons = 0) already match the article.
  • Case 218 — (a) notes say the husband fired, but the Daily Star article quotes Amouranth herself ("I believe I shot one of them"); (b) theft = 0 but a MacBook WAS taken (she tracked it via Find My).
  • Case 221 — date = March 23 but the article says March 24 (twice); reconcile the day.
  • Case 252 — description "tortured for 4 days" and "possible mistaken identity" are not in the linked Bitcoin.com article (it says only: held several days, found tied up). Confirm or soften.
  • Case 253 — flags all = 0 but the source shows an abduction, assault (hospitalised), firearm threat and a forced crypto transfer → should be kidnappings 1, violence 1, weapons 1, theft 1.
  • weapons = 0 but a weapon was involved: 321, 323 (gunpoint); 290 (knifepoint/blunt objects); 242 (knives + cleaver seized); 243 (tased); 245 (weapon recovered).
  • theft = 0 but property was taken: 303 (Dh183k + phones/cheques); 297 (Dh1.7m cash); 273 (dog, MacBook, jewellery); and see 218 above.
  • kidnappings flag — RULE CHANGE 2026-09-06. The flag is the DETENTION flag (victim held against their will, any place, any duration), not "abduction". Please rename the DB field kidnappings to detention and the sheet column "Kidnappings" to "Detention"; the scenario name "Kidnapping" stays. Full rule: README-START-HERE.md, "Definitions". Per-case proposals with evidence: detention-flag-review.md / detention-flag-corrections.json (40 records; on 2026-09-06 the owner ACCEPTED all 30 set-to-1 proposals (rule clarified: detention of anyone, guards or staff included, counts); on 2026-09-07 the owner set 354, 355 and 124 to 0 and withdrew the other set-to-0 proposals under the forced-entry rule; no open items). This REPLACES the earlier item "kidnappings = 1 but no abduction: 293, 271, 273, 298" — under the detention rule 293 and 271 stay 1 (held at gunpoint / forced back inside), 273 goes to 0 (stabbed, not held), 298 needs a source check.
  • Case 237 — violence_torture = 0 but the source says he was beaten; theft = 1 though nothing was taken (released once found "broke").
  • Case 228 (NYC SoHo torture) — the linked ABC source withholds the victim's name; the DB victim field carries "Michael V.T. Carturan". Confirm the name against a primary document before relying on it.

Sheet-article furniture trim — deferred / accepted items (from the 2026-08-26 pass)

Most furniture was removed cleanly. A few items were left, deliberately:

  • Salford cluster (162, 169, 307, 354, 355) — these share one Manchester Evening News article (sheet row 164) embedded via the special shared-source path, so the furniture trimmer did not touch it. It carries a few photo captions ("(Image: GMP)", "(From top left to right) - Scott Armstrong…"). Low severity; trim row 164 once, and all five inherit it.
  • Other-case CONTENT (not furniture) left in, to revisit with the round-up bucket: 235 Article 2 (France24 arrest piece names the Balland/Noizat incidents — see case 209), 254 Article 2 (references the Las Vegas case 323 and a France case as context). These are coherent articles about a suspect/trend, so cutting is a judgment call, not furniture.
  • Accepted intra-line furniture (cannot remove without editing inside a line, which would break the verbatim-line guarantee): case 204 (a Thai "read the original" link is appended to the last body sentence), case 218 ("Article continues below"/"View 4 Images" prefixes are fused onto body sentences).
  • Residual furniture the automated scan missed (add to sheet-trim-decisions.json next pass): 362 (sheet row 259: "Share / Article / Suggestions" nav lines); 353 (sheet row 133: a trailing "Подробнее на Bits.media: " line); 244 (sheet row 245, Article 2: a truncated "Read more at " stub).

Source gaps found by the reconciliation sweep (add to manual queue)

  • Case 66 (Exxon Gas Station, East Lansdowne PA, 2020) — DB url is a Facebook video (facebook.com/watch), not an article. Find a text source.
  • Case 260 (Nate Geier, Singapore, Oct 2025) — DB url is the victim's own X post (x.com/nategeier). Not an extractable article; find reporting or treat the post as a primary quote.
  • Case 358 (35-y-o Chinese man, Bangkok kidnap, Nov 2025) — DB url is WRONG: it points to an unrelated thethaiger dog-in-floods story. Correct the URL AND find the real source.
  • Case 399 (Young trader, Dominican Republic, Oct 2025) — no url in the DB at all and no spreadsheet article. Sourceless; find one from scratch.
Reference in New Issue View Git Blame Copy Permalink