# Handover for Sofia: finishing the K&R database corrections Written 6 October 2026. Everything in this package is a proposal or a ruling on paper. Nothing has been changed in the database from our side, and the database stays the record. ## Where things stand The live database held 399 cases when we pulled it on 6 October 2026. Our verification covers the 398 cases of the 30 September export; case 497 (Montevideo) arrived on 5 October and is untouched. | Item | Count | |---|---| | Cases with a verified summary and a scenario sequence | 398 | | Cases whose record fields were compared with the articles | 328 | | Record-versus-article contradictions found | 1,031 on 315 cases | | Cases with at least one ruling to apply | 307 (350 ruling lines) | | Flag proposals | 429 on 230 cases | | Cases where the verified sequence differs from the `scenario` field | 202 | | Cases with nothing to do | 28 | None of the 316 yes-or-no flag proposals had reached the live database on 6 October, and the six known defects we spot-checked (321, 176, 23, 295, 457, 470) were all still there. Treat every ruling as unapplied until you see it in the record. An earlier version of the verification report said 1,221 contradictions and 369 verified cases. Both figures were double counts. The report in this package is corrected. ## What is in the package All paths are the ones the ruling files cite, so every reference inside them resolves. | Path | What it is | How you use it | |---|---|---| | `merge-output/WORKLIST-BY-CASE.md` | One block per case: rulings, flag proposals, live scenario against verified sequence, holds | Your main working file | | `merge-output/worklist-tracker.csv` | One row per case with counts and empty `done` and `notes` columns | Tick off as you go | | `merge-output/corrections-approved.md` | Every ruling by the owner and by the DA, in the order taken | The authority when a worklist line is unclear | | `merge-output/DEFINITIONS.md` | Glossary and the owner's rules (detention, Authority Misuse, Kidnapping versus Express Kidnapping, targeting vector) | Read once before starting | | `merge-output/batches/contradictions-current.md` | The 1,031 contradictions, record value beside the article quote | Evidence for a ruling | | `merge-output/batches/batch-NN.json`, `decisions-NN.md`, `check-NN.md` | Per-batch verification data, triage decisions and checker notes | Evidence | | `merge-output/batches/flag-proposals.json` | Every flag proposal with its quote | Evidence | | `merge-output/batches/VERIFICATION-REPORT.md` | Counts by field, label gaps, cases no label fits | Overview | | `merge-output/scenario-sequences.json` | Verified sequence, attempted labels and gap notes per case | Source for the new structure | | `merge-output/summary-overrides.json` | Verified summary per case | Already rendered into the dossiers | | `merge-output/sources/` | 398 dossiers: the record block, the verified summary and every article on file | Read the article before changing a field | | `merge-output/sofia-worklist.md` | The manual fetch list and older notes | Source fetching (see below) | | `merge-output/disputed-scenarios.md` | The cases that fitted none of the eleven labels, with what happened in each | Decided on 6 October; background for the Burglary cases | | `merge-output/exports/gart-kr-database-2026-10-06.xlsx` | Colour-coded sheet of the 398 cases | Overview; one case behind live | | `attacks-live-api-2026-10-06.json` | Public API pull of 6 October | What we compared against | | `attacks-export-Gart-website.json` | Our copy of the 30 September export | Stale on `reports`, `notes`, `money_wanted`, `coin_type`, `original_date` | | `merge-output/pending-database-fixes-Sofi.md` | Your own list as we received it on 30 September | Compared below | Left out on purpose: the raw fetch folder (`staging/`), the build scripts, and `contradictions-ALL.md`, which still carries 83 superseded entries. ## How to work a case 1. Open the case block in `WORKLIST-BY-CASE.md`. 2. Read the ruling lines from top to bottom. They are copied word for word, oldest first. Where two lines disagree, the later one wins. 3. A line marked `(owner)` or `accept` is the owner's decision. A line marked `(DA)` was approved under `batches/DECISION-RULES.md` from an explicit article quote. If a `(DA)` line looks wrong against the dossier, do not apply it; write the case number and the reason in the tracker. 4. Make the change by hand on the admin site, as you do now. 5. Mark the row in `worklist-tracker.csv`. Flag proposals under a case are evidence. Apply a flag change when a ruling line states it, or when the case has no ruling line on that flag and the proposal is a plain 0 or 1 backed by its quote. The Kidnapping and Express Kidnapping moves were ruled as a group (see "Batch 11 decisions" in `corrections-approved.md`), so they have no line per case. The verified sequence in each case block already reflects them. ## Order of work 1. **Merges and deletions.** Move the sources of 386 (Fox News, Daily Mail) onto 295, then delete 386. Merge 446 into 445 and date 445 "10 to 11 May 2026". Merge 440 and 441 into 439 and note the three attempts on consecutive days. Delete 45: the owner removed it on 6 October. 2. **Splits.** 49 keeps the 20 May 2018 kidnapping of the boy; add a record for the 21 August 2018 attempt in Aerorand, Middelburg (Dodged Attack). 38 becomes Irving, 22 March 2018, and Mesquite, 28 March 2018. 3. **Rewrite.** 5 becomes the 27 May 2015 Crown Heights robbery; the Dwayne Richards stabbing leaves the record. 4. **Source fixes.** 476: replace the AseanNow URL that points at case 350. 103: replace the "El Pais, Iustel" credit. Both are spelled out at the end of `sofia-worklist.md`. 5. **Field corrections,** case by case from the worklist. The 53 cases with five or more contradictions carry the most changes; the tracker's `contradictions` column sorts them. 6. **Yes-or-no flags.** 316 proposals, none in live. 7. **Source fetching.** `sofia-worklist.md` lists 65 links the pipeline could not read. Open each in a browser and save the article text with the case number. The paywalled La Provence article serves 457 and 458. ## What to do now and what to leave for the new structure The owner is rebuilding the database structure in parallel. Five kinds of change have no field or value today. Entering them now means entering them twice, so leave them: - **Multi-label sequences.** 165 cases have a verified sequence of two or more labels. Leave `scenario` as it is on those. The 21 cases where one existing label replaces another (176 becomes Home Invasion, for example) can be changed now. - **Burglary.** The owner added a twelfth scenario on 6 October for thefts in which nobody was confronted. It applies to 19 cases: 3, 6, 10, 54, 57, 62, 66, 71, 101, 105, 112, 158, 198, 21, 349, 99, 383, 449 and 450. Set it once the database offers the value. On 54, 71 and 158 the theft failed, so they carry two labels: Burglary, then Dodged Attack. The definition is at the end of `merge-output/DEFINITIONS.md`. - **Flag values other than 0 and 1.** 113 proposals read "unconfirmed", "unverified" or "threat only". Leave the flag as it is. - **Links between records.** 430 with 138, 145 and 156; 106 with 124. - **Targeting vector.** Mentioned in many ruling lines; it has no field yet. The Burglary label is the owner's ruling. The other four rules are the DA's working instructions for the transition, and the owner has not ruled on them. ## Where your list and ours differ Your list and our rulings were written separately. Your "Done" items on public fields match the live database. These nine cases need care: | Case | Your item | Our ruling | What to do | |---|---|---|---| | 482 | `reports` and `notes` swapped; `url_3` duplicates `url` | `theft` and `weapons` unconfirmed (owner) | Apply yours. Ours waits for the new flag values. No conflict | | 478 | Leading space in `reports` | Date kept and marked approximate; flags unchanged | Apply both | | 481 | `life_taken`: 4 people, or 5 with the dog? | Stays 5: four homicides plus the charged termination of the pregnancy; the dog is not counted (DA) | Leave at 5 until the owner confirms that the unborn child counts | | 321 | `weapons` 0 to 1 (Yahoo Finance) | `victim` becomes the mother; still "Crypto manager" in live | Apply both. Add the Yahoo Finance article to the record's links; it is not in our dossier | | 258 | Full rewrite from four new sources; three attackers | Rewrite from Ukrinform, Hromadske Radio, Sud.ua and ATN; three detained, at least five involved per police | Use your figures, and state "three detained, at least five involved". Your life.kyiv.ua link is cut off | | 23 | Date fixed to September 1, 2018; `month` to 9 | Date 2 September 2018, about 1:45 a.m.; 1 September was the dinner the evening before. `month` 9. `violence_torture` 1, `drugs_alcohol` 1 as alleged | `month` to 9 now. Check the date against the dossier before choosing | | 358 | `url_4` duplicates `url_3`; trailing space in `location` | Same findings, plus date 1 November 2025 and source changes | Apply both. Both defects were still in live on 6 October | | 176 | Marked optional: location, seven men, `violence_torture` 1; your sources say S$4.9M | Owner accepted: location King Albert Park, scenario Home Invasion, amount SGD 4.34M | It is approved work. Apply ours, and log the 4.9M against 4.34M difference in the tracker. We have not read your two sentencing articles | | 106 | Do not change `theft`; no source describes a November 2021 gunpoint incident | `theft` stays 0. Description from the November 2021 passage in the Krebs piece: armed deputies in a van tried to take his phone (owner) | Flags agree. On the description, read the Krebs article in the dossier | Your list does not carry the approved items for 307, 456, 457, 460, 462 and 295. They are in the worklist. We cannot see `reports`, `notes`, `money_wanted`, `coin_type` or `original_date` through the public API, and the admin site returned 401 to us on 30 September. Your claims on those fields for 482, 478, 480, 488, 23 and 358 are unchecked on our side. ## On hold, waiting for the owner - **24 and 195:** the owner keeps both in the database. Neither has a label yet, so leave `scenario` as it is. - **481:** whether the unborn child counts in `life_taken`. - **458:** the Gardanne attack of the same night gets a record only once someone has read the La Provence article. ## Not finished on our side - **20 cases rewritten from new sources in batch 35** have 107 fresh contradictions and no rulings yet: 16, 103, 113, 114, 223, 373, 390, 399, 408, 412, 419, 427, 430, 434, 436, 444, 448, 465, 476 and 485. Earlier rulings on them stand; the new contradictions are in `batches/contradictions-35.md`. Skip the field corrections on these until the triage is done. - **70 cases between 218 and 372** had their summaries verified by the older method. Their record fields were never compared with the articles, so 68 of them show no rulings. That means unchecked, not clean. - **Case 497** has no dossier, verified summary or sequence. - **Sheet row 252** (Phuket, August 2025) is listed as missing from the database in `cases-missing-from-database.json`. It looks like the same event as DB 476. Unconfirmed. ## What we need back from you 1. A full admin export after each working session, so we can compare the hidden fields and mark what is applied. 2. The tracker with your `done` marks and notes. 3. The article text for every link you open from the fetch list, with the case number. 4. Any `(DA)` line you chose not to apply, with the reason.