feat(verify): batch 35 applied (20 re-sourced cases rewritten and checked); sequences for 412, 408, 223, 436, 434; export regenerated

This commit is contained in:
StellarCrow
2026-10-01 12:59:30 +02:00
parent fba5ae750d
commit 0f7a691151
31 changed files with 1347 additions and 546 deletions
+214 -72
View File
@@ -1,4 +1,4 @@
# Verification report — all batches (2026-09-30)
# Verification report — all batches (2026-10-01)
Every summary, scenario sequence, flag proposal and contradiction below was written from the case's own dossier (sources/<id>_*.txt) by a writer agent and checked line by line by a read-only checker. The DB export is untouched: everything here is a proposal for Sofia. Per-batch detail sits in contradictions-NN.md; the merged list is contradictions-ALL.md.
@@ -9,35 +9,46 @@ Every summary, scenario sequence, flag proposal and contradiction below was writ
| Cases in the DB export | 398 |
| Cases with a verified summary (summary-overrides.json) | 398 |
| Cases with a scenario sequence (scenario-sequences.json) | 398 |
| Cases verified in batches 01–34 | 329 |
| Cases verified in batches 01–35 | 369 |
| Cases still without a verified summary | 0 |
| Record-only cases (no usable article on file) | 4 [11, 45, 66, 399] |
## Contradictions between record and articles
1007 contradictions across 314 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
1221 contradictions across 315 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
| Field | Contradictions |
|---|---|
| description | 155 |
| date | 147 |
| amount | 96 |
| victim | 84 |
| location | 82 |
| attackers | 80 |
| money_wanted | 51 |
| weapons | 43 |
| arrests | 38 |
| notes | 37 |
| detention | 37 |
| description | 185 |
| date | 173 |
| amount | 118 |
| attackers | 108 |
| location | 98 |
| victim | 96 |
| money_wanted | 57 |
| arrests | 50 |
| weapons | 49 |
| violence | 48 |
| detention | 45 |
| notes | 43 |
| scenario | 37 |
| violence | 36 |
| theft | 30 |
| coin_type | 17 |
| theft | 36 |
| coin_type | 19 |
| status | 10 |
| site summary | 8 |
| flags | 7 |
| drugs_alcohol | 5 |
| money fields | 2 |
| how it ended | 2 |
| time of day | 2 |
| entry | 2 |
| lure | 2 |
| description of the police response | 2 |
| motive | 2 |
| victim condition | 2 |
| arrest place | 2 |
| vehicle | 2 |
| attackers at the scene | 2 |
| victims | 1 |
| location of the abduction | 1 |
| location of arrest | 1 |
@@ -48,26 +59,26 @@ Every summary, scenario sequence, flag proposal and contradiction below was writ
Cases with the most contradictions (each needs a full re-entry):
- case 103 (Zaryn Dentzel): 21
- case 408 (Yong Wang, Chinese businessman ): 21
- case 444 (25-year-old wife of a crypto investor): 20
- case 434 (Young Pakistani male): 20
- case 412 (Mainland Chinese businessman, 25): 19
- case 485 (Sylwester Suszek): 18
- case 476 (Aleksandr, 28 y/o Russian national): 16
- case 390 (60 y/o female physician): 16
- case 436 (57 y/o woman): 15
- case 430 (Unidentified man): 15
- case 419 (Family): 15
- case 223 (Anson Que and his driver, Armanie Pabillo): 14
- case 399 (Young trader): 14
- case 16 (Jameson Lopp): 13
- case 373 (Father of a young entrepreneur): 13
- case 465 (Ashley James O'Brien): 12
- case 407 (William Sean "Tony" Creighton, CEO of 5Dimes): 10
- case 405 (David Princay, CEO of Binance France): 8
- case 358 (35 year old Chinese man): 8
- case 12 (Rocelo Lopes' wife): 7
- case 433 (Crypto Forum Moderator): 7
- case 412 (Mainland Chinese businessman, 25): 7
- case 411 (Igor Komarov): 7
- case 408 (Yong Wang, Chinese businessman ): 7
- case 209 (David Balland & Wife): 7
- case 199 (Igor Lermakov): 6
- case 32 (Shailesh Bhatt): 6
- case 23 (T.W. (Troy Woody Jr.)): 6
- case 459 (Stephanie Mau-Asum and Astrid Robinson ): 6
- case 444 (25-year-old wife of a crypto investor): 6
- case 434 (Young Pakistani male): 6
- case 428 (Mother and son (~10 years old)): 6
- case 409 (NFT collector and crypto trader "Sillytuna"): 6
- case 403 (Male cryptocurrency holder): 6
- case 402 (Two adults): 6
- case 201 (Stéphane Winkel's Wife): 5
- case 427 (Family ): 9
- case 113 (34 y/o teacher): 8
- case 448 (Father of influencer Killian Desnos (alias "TeufeurS")): 8
## Flag proposals
@@ -80,12 +91,11 @@ Cases with the most contradictions (each needs a full re-entry):
| drugs_alcohol | 0 | unverified | 4 |
| drugs_alcohol | 0 | 1 | 4 |
| drugs_alcohol | 1 | 0 | 2 |
| kidnappings | 0 | 1 | 42 |
| kidnappings | 0 | 1 | 43 |
| kidnappings | 1 | 0 | 6 |
| kidnappings | 1 | unconfirmed | 4 |
| kidnappings | 0 | unverified | 3 |
| kidnappings | null | 0 | 3 |
| kidnappings | 0 | unconfirmed | 1 |
| kidnappings | 1 | unverified | 1 |
| life_taken | 0 | unverified | 4 |
| life_taken | null | unconfirmed | 3 |
@@ -103,36 +113,35 @@ Cases with the most contradictions (each needs a full re-entry):
| theft | 0 | unconfirmed | 1 |
| theft | null | 1 (inferred) | 1 |
| violence_torture | 0 | 1 | 26 |
| violence_torture | null | 0 | 16 |
| violence_torture | null | 0 | 17 |
| violence_torture | 1 | threat only | 6 |
| violence_torture | 1 | 0 | 6 |
| violence_torture | null | unconfirmed | 6 |
| violence_torture | 1 | unconfirmed | 5 |
| violence_torture | null | unconfirmed | 5 |
| violence_torture | 0 | unconfirmed | 3 |
| violence_torture | null | 1 | 3 |
| violence_torture | 0 | unverified | 2 |
| violence_torture | null | threat only | 2 |
| violence_torture | 1 | unverified | 2 |
| violence_torture | null | threat only | 2 |
| violence_torture | null | 0 (threat and restraint only) | 1 |
| weapons | null | 0 | 33 |
| weapons | 0 | 1 | 32 |
| weapons | null | 0 | 32 |
| weapons | 1 | unconfirmed | 22 |
| weapons | 1 | 0 | 12 |
| weapons | null | 1 | 9 |
| weapons | null | unconfirmed | 8 |
| weapons | null | unconfirmed | 7 |
| weapons | 0 | unverified | 2 |
| weapons | 1 | unverified | 2 |
| weapons | 0 | unconfirmed | 1 |
| weapons | 1 | unconfirmed for this incident | 1 |
Detention (DB field kidnappings) 0/null → 1 under the owner's rule (42): [4, 8, 19, 20, 25, 28, 29, 33, 41, 42, 43, 46, 63, 64, 77, 82, 90, 93, 109, 139, 143, 147, 152, 164, 167, 169, 171, 180, 181, 182, 183, 185, 197, 200, 209, 241, 380, 405, 417, 479, 483, 486]
Detention (DB field kidnappings) 0/null → 1 under the owner's rule (43): [4, 8, 19, 20, 25, 28, 29, 33, 41, 42, 43, 46, 63, 64, 77, 82, 90, 93, 109, 139, 143, 147, 152, 164, 167, 169, 171, 180, 181, 182, 183, 185, 197, 200, 209, 241, 380, 405, 417, 419, 479, 483, 486]
Detention 1 → 0 (6): [124, 128, 151, 195, 406, 423]
Fatality flag (life_taken) proposals:
- case 45: 0 → unverified — no source on file describes the incident
- case 485: null → unconfirmed — "No body has been recovered. No confirmed sighting has surfaced"; crypto.news says "no publicly cited court judgment has established that he is dead"
- case 12: 0 → 1 — "Armed police officers descended on the location and were able to free the hostage and arrest many of the conspirators, killing one in the process" (Business Insider); the Brazilian accounts report one arrest and no death
- case 11: 0 → unverified — no article on file; the record is the only statement
- case 443: null → unconfirmed — possible foul play is suspected but there is no body and no death is reported; he was still missing as of the latest article
@@ -142,30 +151,31 @@ Fatality flag (life_taken) proposals:
- case 411: 1 → unconfirmed — 'Police have not yet confirmed that the body belongs to Komarov and are conducting DNA testing' (Pravda); the coroner said identification was impossible due to advanced decomposition and police had only a partial tattoo match
- case 355: null → 0 — no death
- case 354: null → 0 — no death
- case 485: null → unconfirmed — 'Od czterech lat uważany jest jednak za osobę zaginioną, a nie zmarłą' (Rzeczpospolita); 'no publicly cited court judgment has established that he is dead' (crypto.news)
## Scenario sequences
| Item | Count |
|---|---|
| Cases with more than one label in sequence | 152 |
| Cases where the v1 label is not supported by the file | 49 |
| Cases with more than one label in sequence | 162 |
| Cases where the v1 label is not supported by the file | 46 |
| Foiled attacks (Dodged Attack) | 56 |
| Cases no label fits (empty sequence) | 23 |
| Cases no label fits (empty sequence) | 19 |
Label frequency across all sequences:
| Label | Uses |
|---|---|
| Kidnapping | 133 |
| Home Invasion | 115 |
| Kidnapping | 148 |
| Home Invasion | 117 |
| Authority Misuse | 68 |
| Malicious Invitation - SocialEng | 66 |
| Authority Misuse | 65 |
| Dodged Attack | 56 |
| P2P Trade Gone Wrong | 36 |
| Armed Robbery in Public Space | 25 |
| Costly Fame | 19 |
| Express Kidnapping | 18 |
| P2P Trade Gone Wrong | 41 |
| Armed Robbery in Public Space | 24 |
| Costly Fame | 20 |
| Assault - Mugging | 8 |
| Express Kidnapping | 7 |
| Swatting | 2 |
Cases no label fits, with the writer's reason:
@@ -173,7 +183,6 @@ Cases no label fits, with the writer's reason:
- case 3 (Martin Wismeijer): Both incidents are forced-entry thefts of hardware from closed businesses — no weapon, no confrontation, nobody present — so Armed Robbery in Public Space fails on both "armed" and the presence of anyone to rob, and no other label in the glossary fits.
- case 6 (Robert Nederhoed): The machine was torn from its anchors and carried out of the café during the night with nobody present and no weapon, so the record's Armed Robbery in Public Space label is not supported.
- case 10 (Tivoli Brasserie): The machine was lifted and carried out with nobody present and no weapon, so the record's Armed Robbery in Public Space label is not supported.
- case 11 (Josoj): Record-only: the sole linked source is a podcast reference with no article text, so no label can be tested against anything — marked unsupported for lack of evidence, not because P2P Trade Gone Wrong looks wrong.
- case 21 (Unidentified): The record's Armed Robbery in Public Space is contradicted by the file: no weapon, no victim present, no confrontation and no public space, but a planned night entry into a data centre using a recruited guard's codes.
- case 24 ("Dallas"): The record's Armed Robbery in Public Space is not in the file: nothing was stolen or demanded, the accused was the buyer who wanted the sale called off, and the shot was fired inside a private condo during an argument.
- case 45 (Austin Nedved): Nothing on file describes any incident on 6 July 2018, so no label can be supported: the Swatting scenario, the armed home invasion in the description and the date itself all rest on material that is not in this file.
@@ -188,11 +197,8 @@ Cases no label fits, with the writer's reason:
- case 198 (Coinflip ATM): Overnight ram raid on a closed shopping centre and theft of the machine itself; nobody was present and no one was threatened, so the record's Armed Robbery in Public Space label is not supported.
- case 349 (Unidentified 31 y/o): Overnight burglary of an unoccupied mining garage; no weapon, no one present. None of the eleven labels fits; the record's Armed Robbery label is not supported.
- case 383 (Undisclosed): Home Invasion requires occupants held on site, and no person appears in the account at all: the only conduct described is an unlawful entry and the theft of a device, coordinated by tracking the victim's location in real time, with nobody confronted, restraine
- case 399 (Young trader): Record-only: no article, no linked source and no statement text on file, so the Malicious Invitation label cannot be tested against anything - marked unsupported for lack of evidence, not because the label looks wrong (it is the most plausible reading of the r
- case 409 (NFT collector and crypto trader "Sillytuna"): Home Invasion needs the victim's own private space and no source in this file gives any location at all — not the Hoxton-style address the record carries, not a country; what the file supports is an armed, violent coercion of a $24 million transfer on the vict
- case 449 (Unidentified): The DOJ account is a break-in and a hardware-wallet theft with no occupant, confrontation or holding, so Home Invasion by the glossary's definition does not hold (as in 99 and 450) — BleepingComputer's phrase "home invader" is a characterisation of Ferro's rol
- case 450 (Undisclosed): Nobody was home by design — the co-conspirators waited for the iCloud signal that the victim had left — so the record's Home Invasion label does not hold (the same problem as 99), and no other label fits a burglary of empty premises.
- case 468 (Harry Chun Tak Yeh): No article on file describes an intruder, a confrontation or anyone being held; police were running accident, suicide and homicide in parallel and had not determined how Yeh fell, so the record's Home Invasion label is not supported and none of the eleven labe
## Label gaps (what the eleven scenarios cannot express)
@@ -200,25 +206,25 @@ Gap notes grouped by theme. Counts are notes, not cases; a case can raise severa
| Theme | Notes | Cases |
|---|---|---|
| Repeat victimisation / several incidents on one record | 43 | 9, 18, 32, 38, 49, 72, 106, 134, 162, 169, 179, 184, 185, 203, 209, 223, 254, 257, 259, 354, 355, 357, 374, 395, 423, 436, 439, 440, 441, 446, 463, 466, 467, 470, 471, 472, 483, 487, 493 |
| Insider, intimate or acquaintance perpetrator | 42 | 13, 21, 33, 43, 46, 59, 69, 70, 81, 97, 108, 116, 130, 133, 139, 152, 153, 170, 179, 186, 194, 204, 212, 257, 373, 376, 385, 386, 391, 396, 407, 444, 447, 448, 451, 454, 455, 457, 458, 475, 486 |
| Empty premises, unattended machines, infrastructure | 41 | 2, 3, 6, 10, 11, 19, 21, 38, 51, 54, 57, 62, 66, 71, 84, 85, 101, 102, 105, 112, 158, 198, 352, 383, 389, 399, 420, 449, 450 |
| Extortion at a distance or threat at the door without entry | 10 | 139, 144, 190, 318, 354, 355, 412, 419, 423, 457 |
| Repeat victimisation / several incidents on one record | 47 | 9, 18, 32, 38, 49, 72, 106, 134, 162, 169, 179, 184, 185, 203, 209, 223, 254, 257, 259, 354, 355, 357, 374, 395, 423, 436, 439, 440, 441, 446, 463, 466, 467, 470, 471, 472, 483, 487, 493 |
| Insider, intimate or acquaintance perpetrator | 56 | 13, 21, 33, 43, 46, 59, 69, 70, 81, 97, 103, 108, 116, 130, 133, 139, 152, 153, 170, 179, 186, 194, 204, 212, 257, 373, 376, 385, 386, 391, 396, 407, 430, 444, 447, 448, 451, 454, 455, 457, 458, 465, 475, 486 |
| Empty premises, unattended machines, infrastructure | 43 | 2, 3, 6, 10, 11, 19, 21, 38, 51, 54, 57, 62, 66, 71, 84, 85, 101, 102, 105, 112, 158, 198, 352, 383, 389, 390, 399, 420, 449, 450 |
| Extortion at a distance or threat at the door without entry | 14 | 139, 144, 190, 318, 354, 355, 399, 412, 419, 423, 457 |
| Lured to and held at the attackers' venue (captivity without transport) | 11 | 15, 53, 60, 110, 157, 162, 181, 200, 213, 215, 461 |
| Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation) | 12 | 50, 90, 93, 104, 109, 117, 164, 182, 258, 385, 448, 492 |
| Preparation: leaks, surveillance, trackers, data breaches | 19 | 83, 91, 121, 123, 145, 156, 183, 184, 185, 384, 422, 445, 446, 453, 469, 472, 490, 493 |
| Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation) | 20 | 50, 90, 93, 104, 109, 117, 164, 182, 258, 385, 399, 434, 436, 444, 448, 492 |
| Preparation: leaks, surveillance, trackers, data breaches | 27 | 83, 91, 121, 123, 145, 156, 183, 184, 185, 384, 419, 422, 427, 434, 436, 445, 446, 453, 469, 472, 490, 493 |
| Drugging as the approach | 4 | 48, 88, 92, 97 |
| Unexplained death or undetermined circumstances | 12 | 26, 58, 207, 295, 392, 400, 443, 467, 468, 485 |
| Unexplained death or undetermined circumstances | 14 | 26, 58, 207, 295, 392, 400, 443, 467, 468, 485 |
| Security measures deciding the outcome | 8 | 126, 186, 257, 439, 440, 441, 473, 493 |
| Scope: fraud, non-violent, or not crypto-linked | 16 | 8, 18, 27, 39, 42, 56, 61, 73, 83, 89, 94, 137, 150, 260, 394, 398 |
| Multiple victims, proxy victims or one victim field | 10 | 23, 24, 26, 39, 74, 387, 401, 404, 427, 431 |
| Amount and coin fields cannot split crypto from cash, goods or fiat | 24 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 133, 181, 188, 254, 255, 357, 358, 384, 407, 412, 465, 471, 486, 490, 496 |
| Multiple victims, proxy victims or one victim field | 12 | 23, 24, 26, 39, 74, 387, 401, 404, 427, 431 |
| Amount and coin fields cannot split crypto from cash, goods or fiat | 28 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 133, 181, 188, 254, 255, 357, 358, 384, 407, 412, 465, 471, 486, 490, 496 |
| Control moves between places; one venue field | 5 | 5, 401, 412, 444, 460 |
| Outcome after the transfer (killing, escape, rescue) is not an initiation label | 9 | 52, 84, 147, 166, 201, 361, 366, 432, 458 |
| Crypto link or complainant account is itself unverified | 7 | 96, 175, 178, 199, 399, 400, 443 |
| Initiation or entry method not reported | 6 | 141, 223, 409, 454, 477, 485 |
| Initiation or entry method not reported | 8 | 141, 223, 409, 454, 477, 485 |
| Remote operator, phone drained after the event, or company infrastructure | 4 | 28, 164, 196, 211 |
| Other | 434 | 1, 3, 4, 5, 7, 8, 11, 12, 13, 14, 15, 16, 18, 19, 20, 22, 23, 24, 25, 27, 28, 29, 30, 32, 33, 34, 35, 40, 41, 42, 43, 44, 45, 46, 48, 49, 50, 52, 53, 55, 56, 59, 60, 61, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 76, 77, 78, 79, 80, 81, 82, 85, 86, 88, 89, 90, 91, 92, 93, 96, 99, 102, 103, 104, 105, 106, 108, 109, 110, 111, 113, 114, 116, 117, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 156, 157, 161, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 182, 183, 188, 189, 190, 193, 194, 195, 199, 200, 202, 203, 205, 206, 207, 208, 209, 210, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 413, 414, 415, 416, 417, 418, 419, 421, 422, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 442, 443, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487, 488, 489, 490, 491, 492, 493, 494, 495, 496 |
| Other | 520 | 1, 3, 4, 5, 7, 8, 11, 12, 13, 14, 15, 16, 18, 19, 20, 22, 23, 24, 25, 27, 28, 29, 30, 32, 33, 34, 35, 40, 41, 42, 43, 44, 45, 46, 48, 49, 50, 52, 53, 55, 56, 59, 60, 61, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 76, 77, 78, 79, 80, 81, 82, 85, 86, 88, 89, 90, 91, 92, 93, 96, 99, 102, 103, 104, 105, 106, 108, 109, 110, 111, 113, 114, 116, 117, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 156, 157, 161, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 182, 183, 188, 189, 190, 193, 194, 195, 199, 200, 202, 203, 205, 206, 207, 208, 209, 210, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 399, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 421, 422, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 442, 443, 444, 445, 447, 448, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487, 488, 489, 490, 491, 492, 493, 494, 495, 496 |
Proposed additions to the vocabulary, in order of how often the gap appears: (1) a `repeat_victimisation` / campaign link between records; (2) an `insider` initiation attribute (relative, partner, driver, guard, friend); (3) a label for attacks on unattended premises and machines (burglary, ATM ram-raid, mining rigs); (4) remote extortion with threat but no contact; (5) 'held at attackers' venue' as a Kidnapping sub-type; (6) a `ruse` attribute (delivery, uniform, disguise) separate from Authority Misuse and Malicious Invitation; (7) a preparation phase field (leak, surveillance, tracker).
@@ -240,6 +246,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 185: eleven victims robbed in one event are carried on a single record
- case 203: three people held at the house and one driven hundreds of kilometres away sit on one record with one scenario field
- case 209: two victims held at two separate locations about 200 kilometres apart sit on one record with one location field
- case 223: two victims, one an employee killed alongside his principal, sit on one record
- case 223: two victims, one an employee killed alongside his principal, sit on one record
- case 223: two victims, one of them an employee killed alongside his principal, sit on one record
- case 254: the follow-up extortion call two days later is a second event held inside one record with one date
- case 257: two households entered in one operation are held as one record, with one location and one victim field
@@ -251,6 +259,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 395: the campaign that followed - the forced lock, the petrol poured on the door, the Snapchat threats against the mother and sister - has no label, and the person held is not the crypto holder
- case 423: the repeated fake deliveries before and after the attack — four approaches in two hours, and another coffee eight days later — are reconnaissance the labels cannot express
- case 436: the group's planned armed reprisal against a Nimes business a week later is a second crime carried on the same record
- case 436: the group's planned armed reprisal against a Nîmes business a week later is a second crime carried on the same record
- case 436: the group's planned armed reprisal against a Nîmes business a week later is a second crime carried on the same record
- case 439: the repeat targeting of the same household four times in about six weeks has no label
- case 439: three attempts on three consecutive days are held as three separate records, but the only source describes them as one series without dates or order
- case 440: the repeat targeting of the same household four times in about six weeks has no label
@@ -280,6 +290,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 70: the ransom was paid by a relative from her own wallet; the record has no field for who paid
- case 81: insider facilitation — reception staff paid and two security guards bribed — has no label
- case 97: an intimate partner as one of the plotters has no label; Malicious Invitation carries the betrayal of trust
- case 103: targeting vector: online lure on top of research (messages posing as a friend of a friend; police say the group had gathered extensive information on him)
- case 103: targeting vector: online lure on top of research (messages posing as a friend of a friend; police say the group had gathered extensive information on him)
- case 108: the attackers included a former employee who knew the household; insider knowledge is not expressed by any label
- case 116: a serving police constable who identified the target from inside the cybercrime cell is insider misuse; Authority Misuse as the glossary defines it needs authority used to gain the victim's compliance, which this report does not describe
- case 130: the target was picked because the gym's operator knew his business - an insider at a place the victim used voluntarily, which no label names
@@ -294,6 +306,10 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 204: an extortion growing out of a prior business dispute between acquaintances has no label
- case 212: prior personal ties or acquaintance between organiser and victim (here her own brother) have no label or field; Malicious Invitation is used for the betrayal of trust
- case 257: the attack was ended by relatives arriving, not by police, and no field records who broke it off
- case 373: CNEWS frames it as a criminal network reclaiming money it says is its own, with arson at the son's girlfriend's home and a one-million-euro demand; a debt or settling-of-scores motive has no label
- case 373: CNEWS frames it as a criminal network reclaiming money it says is its own, with arson at the son's girlfriend's home and a one-million-euro demand; a debt or settling-of-scores motive has no label
- case 373: the person held is a relative of the presumed asset holder, not the holder: extortion of a family member through a proxy victim has no label
- case 373: the person held is a relative of the presumed asset holder, not the holder: extortion of a family member through a proxy victim has no label
- case 373: the person held is a relative of the presumed asset holder, not the holder: extortion of a family member through a proxy victim has no label
- case 376: a relative as the organiser of the abduction has no label
- case 385: the ransom was paid from another country by a relative who was never in danger himself, which the money fields cannot show
@@ -301,8 +317,14 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 391: one of the four already had access to the unit and opened the door for the rest; insider access of that kind has no label and no flag
- case 396: the man held is not the crypto holder - the ransom was aimed at his son's wallet abroad - and the labels describe the holder, not the relative used as leverage
- case 407: insider betrayal — a gang built out of the victim's own trusted staff and their relatives — has no label
- case 430: family members held at gunpoint in the house while only the man was taken away sit behind one detention flag
- case 430: family members held at gunpoint in the house while only the man was taken away sit behind one detention flag
- case 444: extortion aimed at a third party (a husband per France 3, a wealthy friend in Dubai per DNA), not at the person held, is not expressible
- case 444: extortion aimed at a third party (a husband per France 3, a wealthy friend in Dubai per DNA), not at the person held, is not expressible
- case 444: extortion aimed at a third party — a wealthy friend, not the person held — is not expressible
- case 447: a relative of the crypto holder targeted in his place has no label
- case 448: a ransom extorted from a relative (the son in Malta), not from the person held, is not expressible
- case 448: a ransom extorted from a relative (the son in Malta), not from the person held, is not expressible
- case 448: a ransom extorted from a relative rather than from the person held is not expressible
- case 451: extortion aimed at a relative — the ransom was demanded from her son, not from the person held — is not expressible
- case 454: the 14,000 euros came from the victim's partner and a friend rather than from his own holdings, so the loss falls partly outside the named victim with no field to say so
@@ -310,6 +332,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 455: the lure came from a twenty-year friend, not a stranger's pretext, which the label does not distinguish
- case 457: a household targeted for holdings a relative sold more than a year earlier has no field
- case 458: the two women held were not the holder; the relative whose gains were the target has no field
- case 465: targeting vector: acquaintance (the trio met him through mutual acquaintances and learned of his wealth, per the Facebook post); the sequence has no slot for it
- case 465: targeting vector: acquaintance (the trio met him through mutual acquaintances and learned of his wealth, per the Facebook post); the sequence has no slot for it
- case 475: the victim was befriended in a bar and then made to take his attackers to his own home; no label covers a lure that runs in that direction
- case 486: a two-month acquaintance formed at a nightclub and then used as the approach cannot be distinguished from a cold ambush; the report does not say the December meeting was arranged as a trap
@@ -352,6 +376,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 352: the record's Home Invasion label has nothing to rest on: the site was a mining farm under construction, not a residence, and nobody was held
- case 383: the cyber intrusion, the purchased user data and the real-time iCloud tracking that made the burglary possible are the method of this case and have no field
- case 389: the several attempted burglaries against the same family over the Christmas holidays are part of the same targeting and have no field
- case 390: targeting vector: unknown; police are examining whether the intruders acted on targeted or wrong information
- case 390: targeting vector: unknown; police are examining whether the intruders acted on targeted or wrong information
- case 399: the record's own description - lured to an apartment for a cash trade and ambushed there - reads as Malicious Invitation plus captivity at the attackers' premises, but with nothing on file to test it no label is asserted (same treatment as 11, 45 and 66)
- case 420: the labels do not record that the intended target (crypto keys) yielded nothing while a conventional burglary of cash, silver and jewellery succeeded
- case 449: a burglary in which no occupant appears fits none of the eleven labels; Home Invasion in the glossary requires occupants held on site
@@ -365,6 +391,10 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 318: the probe at the door and the armed confrontation days later are split across two records (this one and 433), so the handgun, the spray and the torture kit cannot be counted here
- case 354: extortion by threat at the door, without entry or holding, has no label; tagged Home Invasion as the closest
- case 355: a weapon threat at the door to extort, without entry, sits uneasily under Home Invasion
- case 399: targeting vector: online lure (USDT sale arranged over Telegram); whether he was chosen in advance is not stated
- case 399: targeting vector: online lure (USDT sale arranged over Telegram); whether he was chosen in advance is not stated
- case 412: police classified the case as blackmail and false imprisonment, which none of the eleven labels renders
- case 412: police classified the case as blackmail and false imprisonment, which none of the eleven labels renders
- case 412: police classified the case as blackmail and false imprisonment, which none of the eleven labels renders
- case 419: the file stops at the doorstep, so the labels cannot say whether the attackers ever got inside — the difference between Dodged Attack and Home Invasion here
- case 423: an attack broken by the victim's own physical resistance at the door has no label distinct from the rest of Dodged Attack
@@ -396,6 +426,14 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 182: the pretext was a professional enquiry about a course rather than an invitation to an event, which the Malicious Invitation label covers only loosely
- case 258: the men wore military uniform and posed as recruitment-centre staff while one of those detained really is a serviceman, and no field separates a fake uniform from a real one
- case 385: the accusation of being a scammer — the pretext that made the fake arrest plausible — has no field, and neither does the fact that the complaint reached the real police through a third party
- case 399: the record's own description (lured to an apartment under a trade pretext and ambushed) also reads as Malicious Invitation - SocialEng; the owner chose P2P Trade Gone Wrong because the meeting was a crypto sale arranged online
- case 399: the record's own description (lured to an apartment under a trade pretext and ambushed) also reads as Malicious Invitation - SocialEng; the owner chose P2P Trade Gone Wrong because the meeting was a crypto sale arranged online
- case 434: the uniform-like clothing and the claim that he had to go to a police station after a collision (The News) are a claimed-authority pretext; under the 2026-09-30 Authority Misuse ruling that could make Authority Misuse the initiation label, though The News stresses the uniforms were not police attire (owner decision)
- case 434: the uniform-like clothing and the claim that he had to go to a police station after a collision (The News) are a claimed-authority pretext; under the 2026-09-30 Authority Misuse ruling that could make Authority Misuse the initiation label, though The News stresses the uniforms were not police attire (owner decision)
- case 436: the new sources (France 3 Occitanie, franceinfo, ICI 15 April) now give the entry method: a man posing as a delivery driver got the door opened. Under the ruling of 2026-09-30 and decisions-24 Q2 ('Authority Misuse -> Home Invasion' if the ruse is confirmed), the sequence should become Authority Misuse -> Home Invasion; kept as Home Invasion here because scenario-sequences.json has not yet been changed, for the owner to apply
- case 436: the new sources (France 3 Occitanie, franceinfo, ICI 15 April) now give the entry method: a man posing as a delivery driver got the door opened. Under the ruling of 2026-09-30 and decisions-24 Q2 ('Authority Misuse -> Home Invasion' if the ruse is confirmed), the sequence should become Authority Misuse -> Home Invasion; kept as Home Invasion here because scenario-sequences.json has not yet been changed, for the owner to apply
- case 444: the delivery ruse rests on DNA and on Cryptoast's 'après être allée chercher un colis'; France 3 does not describe how she was seized
- case 444: the delivery ruse rests on DNA and on Cryptoast's 'après être allée chercher un colis'; France 3 does not describe how she was seized
- case 448: the fake Amazon delivery man used to get the door open has no label of its own
- case 492: the law-enforcement legend and the military-pattern uniform are recorded for the group as a whole, at its formation, and are not attributed to the 15 May approach, so Authority Misuse rests on the group's stated method rather than on a described uniform at the scene
@@ -411,8 +449,16 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 184: the preparation phase — weeks of physical and digital surveillance, a GPS tracker, forged passports, a recruited hacker — has no label
- case 185: an inside leak ('someone close to the victims knew about their financial movements') has no label
- case 384: the 15 arrests point to a syndicate with surveillance, drivers and handlers behind three men on the pavement, and the record has no way to show roles
- case 419: targeting vector: data leak (the Waltio breach of January 2026, per Decrypt relaying Le Parisien and Cryptoast's source close to the investigation)
- case 419: targeting vector: data leak (the Waltio breach of January 2026, per Decrypt relaying Le Parisien and Cryptoast's source close to the investigation)
- case 422: the file never states what the attacker intended to demand once inside the garage, only that the victim believed his crypto holdings had been leaked
- case 422: the reconnaissance pattern the victim described (unordered food deliveries, a free driveway-cleaning offer) has no label
- case 427: targeting vector: data leak is the prosecutor's general explanation for the phenomenon, not stated for this house; the attackers apparently worked from an outdated address (former owner)
- case 427: targeting vector: data leak is the prosecutor's general explanation for the phenomenon, not stated for this house; the attackers apparently worked from an outdated address (former owner)
- case 434: new evidence tests the 2026-10-01 ruling that 434 stays Express Kidnapping: the father says the attackers 'had done proper reconnaissance and had complete information' (The News), which, if accepted, makes him a pre-selected victim and the case Kidnapping under the owner's rule; it is the father's inference, not a police finding (owner decision)
- case 434: new evidence tests the 2026-10-01 ruling that 434 stays Express Kidnapping: the father says the attackers 'had done proper reconnaissance and had complete information' (The News), which, if accepted, makes him a pre-selected victim and the case Kidnapping under the owner's rule; it is the father's inference, not a police finding (owner decision)
- case 436: targeting vector: data leak (the authorities mention a leak at Waltio 'dans cette affaire', France 3)
- case 436: targeting vector: data leak (the authorities mention a leak at Waltio 'dans cette affaire', France 3)
- case 445: targeting built on a data leak about the victim's crypto transactions has no label of its own
- case 446: targeting built on a data leak about the victim's crypto transactions has no label of its own
- case 453: surveillance of the victim's daughter is recorded nowhere
@@ -442,6 +488,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 468: an unexplained death of a crypto holder, with a ransacked flat and no established intruder, fits none of the eleven labels
- case 468: the file cannot say whether a crime occurred at all, and the schema has no undetermined state
- case 485: an unresolved disappearance that is only reported as a kidnapping has no label for an unestablished attack; nothing in the file confirms he was taken, only that his family received messages saying so
- case 485: the label rests on a charge of unlawful deprivation of liberty still in force and on messages to the family; police judged the 34-bitcoin voice message a fake, the CBŚP found no evidence of a kidnapping for ransom, a former employee says he left voluntarily with a woman and an investors' detective favours a controlled disappearance, so the file supports neither a taking nor a staged exit conclusively (owner ruling: keep, low-confidence)
- case 485: the label rests on a charge of unlawful deprivation of liberty still in force and on messages to the family; police judged the 34-bitcoin voice message a fake, the CBŚP found no evidence of a kidnapping for ransom, a former employee says he left voluntarily with a woman and an investors' detective favours a controlled disappearance, so the file supports neither a taking nor a staged exit conclusively (owner ruling: keep, low-confidence)
### Security measures deciding the outcome
@@ -483,6 +531,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 387: the cryptocurrencies were her partner's and she was the one tied up and held; the single victim field cannot show that split
- case 401: the women held are not the crypto holder - the target was the partner's business - and the labels describe the holder, not the household used as leverage
- case 404: three victims in one household are held in one victim field
- case 427: the target (a former owner of the house, or a business owner close to the family) was absent and the household was held in his place; the labels do not mark proxy victims or an attack on the wrong or absent holder
- case 427: the target (a former owner of the house, or a business owner close to the family) was absent and the household was held in his place; the labels do not mark proxy victims or an attack on the wrong or absent holder
- case 427: the target was absent and the household was held in his place; the labels do not mark proxy victims
- case 431: the holder was absent and his family was held in his place; the labels do not mark proxy victims
@@ -507,6 +557,10 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 384: no cryptocurrency was taken — the loss was 1 billion yen in banknotes and the crypto nexus is the victims' employer's line of business, which coin_type can only record as '4 briefcases with cash'
- case 407: a ransom paid in part and a victim killed anyway has no field; the record's money_wanted carries both numbers in prose
- case 412: a theft of physical goods (silver) alongside the crypto has no field of its own; the record puts it in coin_type
- case 412: a theft of physical goods (silver) alongside the crypto has no field of its own; the record puts it in coin_type
- case 412: a theft of physical goods (silver) alongside the crypto has no field of its own; the record puts it in coin_type
- case 465: the watch and the crypto are given as one combined loss in one source and as a total with a separate crypto figure in the other; the amount fields cannot hold both
- case 465: the watch and the crypto are given as one combined loss in one source and as a total with a separate crypto figure in the other; the amount fields cannot hold both
- case 465: the £250,000 covers a watch and bitcoin together; the amount fields cannot express a combined loss
- case 471: the record's 'remote mastermind' watching the Snapchat stream appears in no article on file
- case 486: the record cannot hold the split between the crypto ($562,155) and the jewellery (about $413,500)
@@ -551,6 +605,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 454: the record's "garage" is not in the file, which says only a room
- case 477: how long either victim was held is not reported, so the difference between an express pattern and a longer detention cannot be recorded
- case 485: the file cannot say whether the business meeting at the fuel depot was the lure
- case 485: the file still cannot say whether the business meeting at the fuel station was a lure
- case 485: the file still cannot say whether the business meeting at the fuel station was a lure
### Remote operator, phone drained after the event, or company infrastructure
@@ -584,6 +640,12 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 14: the file says nothing about what happened between her boarding the vehicle and her death, so the attack pattern itself is unrecorded
- case 14: the theft happened online after the victim's death, by impersonation, which no scenario label covers
- case 15: the countermeasure that ended the attack — engineering an SOS from his own phone — has no field, although it is the only reason the theft failed
- case 16: motive not established: Lopp names online opponents from the Bitcoin scaling debate but says the caller never referred to them
- case 16: motive not established: Lopp names online opponents from the Bitcoin scaling debate but says the caller never referred to them
- case 16: targeting vector: public profile / media (a vocal Bitcoin engineer), per Lopp's own reading; not established
- case 16: targeting vector: public profile / media (a vocal Bitcoin engineer), per Lopp's own reading; not established
- case 16: the money demand was made of the 911 dispatcher as part of the hoax script, not of the victim; there is no field for a demand aimed at no one
- case 16: the money demand was made of the 911 dispatcher as part of the hoax script, not of the victim; there is no field for a demand aimed at no one
- case 16: the money demand was made of the 911 dispatcher as part of the hoax script, not of the victim; there is no field for a demand aimed at no one
- case 18: the infant present during some of the robberies, which drew child-abuse counts, has no field
- case 19: two hours of mobile detention in a vehicle reads as Express Kidnapping, but the operation was planned around a known holder, which that label excludes
@@ -680,7 +742,11 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 99: theft of a safe from an empty private house has no label; the eleven scenarios all assume a person is present
- case 102: a death caused by a defender's gunfire rather than by the robbers has no label
- case 103: the gang got the phone, the tablet and the code but not the coins; the schema has no way to record a wallet that held because a second person was needed
- case 103: the gang got the phone, the tablet and the code but not the coins; the schema has no way to record a wallet that held because a second person was needed
- case 103: the gang got the phone, the tablet and the code but not the coins; the schema has no way to record a wallet that held because a second person was needed
- case 103: the maintenance technician — a bystander beaten, bound and held for nearly four hours — is not the record's victim and has no place in the row
- case 103: the maintenance technician, a bystander beaten, bound and held for nearly four hours, is not the record's victim and has no place in the row
- case 103: the maintenance technician, a bystander beaten, bound and held for nearly four hours, is not the record's victim and has no place in the row
- case 104: a victim moved through three separate holding places over six days reads as one Kidnapping label
- case 105: force used against bystanders during the getaway, rather than against a victim, has nowhere to go in the schema
- case 106: a private client renting real police power — badges, databases, sworn warrants — has no label beyond Authority Misuse
@@ -691,8 +757,20 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 111: a part-paid ransom traced on-chain to make the arrests has no label; nor does the victim's fate, which the report leaves open
- case 111: the labels cannot express that the official trappings were faked with a green plate while three of the accused were genuine police officials
- case 113: a second victim present only because she happened to be visiting is not expressed by the scenario labels
- case 113: a second victim present only because she happened to be visiting is not expressed by the scenario labels
- case 113: a second victim present only because she happened to be visiting is not expressed by the scenario labels
- case 113: targeting vector: not stated
- case 113: targeting vector: not stated
- case 113: the labels have no way to mark an invasion where the crypto objective failed but the violence and the terror did not
- case 113: the labels have no way to mark an invasion where the crypto objective failed but the violence did not
- case 113: the labels have no way to mark an invasion where the crypto objective failed but the violence did not
- case 114: Dodged Attack does not record how the attack was dodged — here the victim physically fought the man off at his home
- case 114: Dodged Attack does not record how the attack was dodged: here the victim pushed and struck the armed man at his door, then locked himself in
- case 114: Dodged Attack does not record how the attack was dodged: here the victim pushed and struck the armed man at his door, then locked himself in
- case 114: targeting vector: public profile / media (a subscriber of a well-known crypto influencer, TF1)
- case 114: targeting vector: public profile / media (a subscriber of a well-known crypto influencer, TF1)
- case 114: the attacker was one of the victim's own subscribers who found his address and followed him for days (TF1); stalking by an audience member has no label
- case 114: the attacker was one of the victim's own subscribers who found his address and followed him for days (TF1); stalking by an audience member has no label
- case 114: the attacker was one of the victim's own subscribers who found his address and followed him for days; stalking by an audience member has no label
- case 116: the labels do not mark an extortion that collapsed because the perpetrators feared arrest
- case 117: the theft was of cash brought to buy crypto, not of crypto; none of the labels marks which side of the trade the asset was on
@@ -775,7 +853,11 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 209: a ransom paid, then frozen and seized, is a theft that was largely undone, and the theft flag cannot say so
- case 209: the extortion target was a third party, another Ledger co-founder, not either of the people held
- case 210: the file does not say whether the house where he was held was the meeting place itself or somewhere he was taken to; Kidnapping is used for captivity on premises that are not his
- case 223: a ransom paid in tranches and the hostages killed anyway has no field; the outcome column can only say killed
- case 223: a ransom paid in tranches and the hostages killed anyway has no field; the outcome column can only say killed
- case 223: a ransom paid twice and the hostages killed anyway has no field; the outcome column can only say killed
- case 223: the ABS-CBN text now on file has police saying a Chinese female contact was used to lure him to the meeting, which supports Malicious Invitation - SocialEng before Kidnapping; the sequence is left as Kidnapping pending the owner's ruling (the 2026-10-01 trace recommends restoring the lure)
- case 223: the ABS-CBN text now on file has police saying a Chinese female contact was used to lure him to the meeting, which supports Malicious Invitation - SocialEng before Kidnapping; the sequence is left as Kidnapping pending the owner's ruling (the 2026-10-01 trace recommends restoring the lure)
- case 254: the laundering leg through HTX and Kyrrex has no field
- case 255: a remote third party feeding account information to the men in the house by phone has no field
- case 255: the husband was driven three hours to a second property and forced to transfer there, a kidnapping leg inside a home invasion that one scenario field cannot carry
@@ -803,6 +885,12 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 363: the victim was 17 and nothing in the record marks that he was a minor
- case 366: the case was transferred to another country's jurisdiction because extradition was impossible, which the record has no field for
- case 373: filmed captivity used as leverage on a third party is not expressible in the labels
- case 373: filmed captivity used to pressure a third party is not expressible in the labels
- case 373: filmed captivity used to pressure a third party is not expressible in the labels
- case 373: motive not established (owner rule of 2026-10-01, kept, flagged): the crypto link rests on a source close to the investigation (France 3) and a police source (CNEWS), while RTL calls it a hypothesis
- case 373: motive not established (owner rule of 2026-10-01, kept, flagged): the crypto link rests on a source close to the investigation (France 3) and a police source (CNEWS), while RTL calls it a hypothesis
- case 373: targeting vector: family of a holder; how the attackers chose him is not stated beyond 'visiblement l'attendaient'
- case 373: targeting vector: family of a holder; how the attackers chose him is not stated beyond 'visiblement l'attendaient'
- case 374: two of the six suspects are minors, which the record cannot express
- case 375: nothing crypto was taken: the loss is the cash staked for a purchase, which the database's crypto fields cannot hold cleanly
- case 375: the ambush landed during an in-person cash-for-crypto trade, but the file does not say whether the counterparty took part, so P2P Trade Gone Wrong cannot be assigned
@@ -823,8 +911,12 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 388: whether anything was actually taken is never reported, so the theft flag cannot separate a completed robbery from an aborted one
- case 389: control was seized inside his own home and he was moved away at once, so the home phase of the attack carries no separate label
- case 389: whether the attackers got anything is never reported, which the theft flag cannot express
- case 390: the crypto motive is reported only as a possibility ('zouden ... mogelijk uit geweest zijn op cryptomunten', Redactie24 citing HLN) and the victim held no crypto; the schema cannot mark an attack on a mistaken target or an unverified crypto link (owner rule: keep, flagged motive not established)
- case 390: the crypto motive is reported only as a possibility ('zouden ... mogelijk uit geweest zijn op cryptomunten', Redactie24 citing HLN) and the victim held no crypto; the schema cannot mark an attack on a mistaken target or an unverified crypto link (owner rule: keep, flagged motive not established)
- case 390: the crypto nexus of this case is carried only by the headline of a source whose text could not be retrieved, and nothing in the schema can mark a record whose crypto link is unverified
- case 390: the prosecutors' own qualification is attempted extortion plus theft with violence — an extortion that failed while the theft succeeded — which no single label expresses
- case 390: the prosecutors' qualification is attempted extortion plus theft with violence (an extortion that failed while a small theft succeeded), which no single label expresses
- case 390: the prosecutors' qualification is attempted extortion plus theft with violence (an extortion that failed while a small theft succeeded), which no single label expresses
- case 391: the threat to take him out of the country and sell his organs is coercion with no category of its own between Violence/Torture and Weapons
- case 392: the intended target was the son, who was never touched; neither the victim field nor the labels can record an attack aimed at a holder through his parents
- case 393: a family with three children held together to extract one access code has no label distinguishing it from a single-victim invasion
@@ -834,6 +926,10 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 397: the impersonation of Income Tax officers that the record's Authority Misuse label rests on appears nowhere in this case's file
- case 397: the only narrative of the kidnapping on file is a party spokesperson's press conference; there is no field to mark a case whose account is political rather than police or judicial
- case 398: neither article says where Mavani was held or for how long, so nothing in this file carries the record's farmhouse and multi-day captivity
- case 399: Kidnapping rests on his being abandoned in Bonao, in another province, after being tied up in the apartment; no source says how long he was held or how he got there
- case 399: Kidnapping rests on his being abandoned in Bonao, in another province, after being tied up in the apartment; no source says how long he was held or how he got there
- case 399: the case rests on the victim's direct report to Gart Research plus a police release relayed by four outlets; the schema cannot mark a first-hand source
- case 399: the case rests on the victim's direct report to Gart Research plus a police release relayed by four outlets; the schema cannot mark a first-hand source
- case 402: the two who entered say they were themselves coerced over Signal by handlers who never appear at the scene; there is no label or field for a directed or outsourced attacker
- case 403: full recovery of the stolen crypto within 72 hours and its return to the victim has no field
- case 403: the theft of a car alongside the crypto, and the car being what caught them, has nowhere to sit
@@ -846,8 +942,14 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 406: an attack on the wrong address, against someone with no connection to crypto, has no label
- case 406: one commando and two victims on the same morning are held as two records with no link field between them
- case 407: the corrupt traffic stop and the abduction are one operation run by one gang, and the schema takes a single primary scenario
- case 408: Haberler, now on file, carries the dinner lure, the named woman and the four-man team outside the restaurant; the 2026-10-01 trace notes that this supports Malicious Invitation - SocialEng followed by Kidnapping, as the DA's decisions-27 Q1 anticipated; the sequence is left as Kidnapping pending the owner's ruling
- case 408: Haberler, now on file, carries the dinner lure, the named woman and the four-man team outside the restaurant; the 2026-10-01 trace notes that this supports Malicious Invitation - SocialEng followed by Kidnapping, as the DA's decisions-27 Q1 anticipated; the sequence is left as Kidnapping pending the owner's ruling
- case 408: a killing that ends a robbery with no ransom negotiation has no label of its own
- case 408: a killing that ends a robbery with no ransom negotiation has no label of its own
- case 408: a killing that ends a robbery, rather than a ransom negotiation, has no label of its own
- case 408: a woman who passed on the victim's whereabouts without being described as part of the attack has no place in the schema, and no label covers an informant
- case 408: a woman who set up the meeting and stayed at the scene acting unaware has no role field
- case 408: a woman who set up the meeting and stayed at the scene acting unaware has no role field
- case 408: the abduction itself is nowhere in this file, so the label rests on the gap between where he vanished and where he was buried
- case 409: a case whose only account of the physical attack is the victim's own X posts, with two outlets attributing the loss to address poisoning instead, has no way to be marked as uncorroborated
- case 409: the one word that might carry a label is the victim's own 'kidnapping' inside a list of elements, which a second outlet renders as a threat rather than an event
@@ -857,6 +959,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 411: a case where the central facts rest on a ransom video and unnamed sources, with no official confirmation and a live suggestion of staging, has no way to be marked as such
- case 411: a location exposed by a companion's geotagged post is not Costly Fame, which turns on the victim's own public profile
- case 411: an abduction over an alleged criminal debt, where the ransom is framed as repayment rather than a price, has no label
- case 412: CCN, now on file, carries the lure ('had reportedly arranged a meeting with four suspects to discuss what he believed was a legitimate business deal'); by the DA's own test in decisions-27 that supports Malicious Invitation - SocialEng followed by Kidnapping; the sequence is left as Kidnapping pending the owner's ruling
- case 412: CCN, now on file, carries the lure ('had reportedly arranged a meeting with four suspects to discuss what he believed was a legitimate business deal'); by the DA's own test in decisions-27 that supports Malicious Invitation - SocialEng followed by Kidnapping; the sequence is left as Kidnapping pending the owner's ruling
- case 413: an attack that completed the forced entry and the assault but never reached the payment sits between Home Invasion and Dodged Attack; the labels force a choice
- case 414: the fourth man directing the operation by phone from elsewhere has no place in the labels
- case 415: nothing in the labels records that the address was wrong — the household had no connection to cryptocurrency at all
@@ -867,6 +971,12 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 418: Spanish sources call it a "secuestro exprés" while the plan was a transfer to Alicante for torture — the two glossary labels Kidnapping and Express Kidnapping pull in different directions
- case 418: the abduction was completed but the extortion never happened; the labels record one scenario and cannot show that the operation was broken minutes in
- case 419: "fleeing under pressure from their victims" implies a confrontation the labels cannot describe
- case 419: Decrypt (relaying Le Parisien) puts the beating outside the flat after the husband came out; Cryptoast and Bourse Inside put it inside after the door was shut. Home Invasion rests on the latter, as the owner ruled
- case 419: Decrypt (relaying Le Parisien) puts the beating outside the flat after the husband came out; Cryptoast and Bourse Inside put it inside after the door was shut. Home Invasion rests on the latter, as the owner ruled
- case 419: the attack ended when the daughters upstairs called the police; how an attack was cut short is not expressible
- case 419: the attack ended when the daughters upstairs called the police; how an attack was cut short is not expressible
- case 419: the charge includes attempted kidnapping ('tentative d'enlèvement en bande organisée'); an intended abduction that did not happen has no label
- case 419: the charge includes attempted kidnapping ('tentative d'enlèvement en bande organisée'); an intended abduction that did not happen has no label
- case 421: the file disagrees with itself on whether the men got as far as forcing the building door, which is what separates an attempt at the threshold from a break-in
- case 421: the plot was broken by a concierge, not by the victims, and Dodged Attack carries a suggestion of victim awareness this case does not support
- case 422: Dodged Attack does not express that the attacker had already drawn a gun and landed a blow before the interruption
@@ -880,19 +990,29 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 428: a child as a co-hostage is not expressible
- case 428: the transfer delay that made the gang switch from on-site extortion to hostage-taking has no label
- case 429: an attack that gains control inside the home and is then broken by the victim fits neither Home Invasion nor Dodged Attack cleanly
- case 430: one incident inside a 14-defendant, multi-state prosecution has no field for its place in the series (linked to 138, 145, 156)
- case 430: one incident inside a 14-defendant, multi-state prosecution has no field for its place in the series (linked to 138, 145, 156)
- case 430: one incident inside a 14-defendant, multi-state prosecution has no label for its place in the series
- case 430: the record's claim that the gang failed to find the bitcoin has no counterpart in the labels
- case 430: the record's claim that the gang failed to find the bitcoin has no source and no counterpart in the labels
- case 430: the record's claim that the gang failed to find the bitcoin has no source and no counterpart in the labels
- case 431: children among the detained victims is not expressible
- case 432: the roadside interception that starts the abduction has no label of its own
- case 433: a first approach at his door four days earlier, which he repelled by shutting it, is folded into the same record as the car incident
- case 433: the aftermath has nowhere to go: a family in hiding between short-term rentals, the accused on house arrest, a youth-protection referral
- case 433: the defensive measures decided the outcome — the bear spray bought after the first approach, the call to police kept open — and nothing records that
- case 434: a whole case told only through the victim's father has no way to be marked as second-hand
- case 434: the account is still mainly the father's; the SSP relays the victim's report only in outline
- case 434: the account is still mainly the father's; the SSP relays the victim's report only in outline
- case 434: the hired driver's refuelling stop is still the hinge of the attack and no source says whether the driver was involved
- case 434: the hired driver's refuelling stop is still the hinge of the attack and no source says whether the driver was involved
- case 434: the ride-hailing trip as the point of interception has no label; the driver's petrol-pump stop is the hinge of the whole attack and nothing records whether the driver was involved
- case 435: a case known only through a prosecutor's aggregate statement has no way to record that the facts themselves are unreported
- case 435: the file has a charge sheet and no incident: no victim, no venue, no duration, no amount, no account of how it happened
- case 435: two of the three accused are charged over a second kidnapping a month later at the other end of the country; the serial offender has no label
- case 436: recruitment of young men by a named criminal organisation has no label
- case 436: recruitment of young men for 'missions' on social networks by a named criminal organisation has no label
- case 436: recruitment of young men for 'missions' on social networks by a named criminal organisation has no label
- case 436: the sources give a violent sequestration at the victim's home with no entry method at all, so the initiation of the attack is unlabelled
- case 437: a haul abandoned during the escape leaves the theft flag ambiguous
- case 437: a household with no link at all to cryptocurrency, attacked on bad intelligence, has no label
@@ -902,8 +1022,16 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 442: a second team that waited outside and afterwards searched the first team to collect the proceeds has no label
- case 442: the record holds one victim; the source says someone inside opened the door and does not say whether that was the same person who was held
- case 443: impersonation of the victim by text for more than a month, and the stripping and attempted letting of his house, have no label
- case 444: targeting vector: not stated; France 3 says the men were 'mandatés depuis les Bouches-du-Rhône', and no source says how she was identified
- case 444: targeting vector: not stated; France 3 says the men were 'mandatés depuis les Bouches-du-Rhône', and no source says how she was identified
- case 444: where she was held and found is contested (rue du Jura per France 3, the Neuhof forest per DNA and Cryptoast); either way she was taken away in the van
- case 444: where she was held and found is contested (rue du Jura per France 3, the Neuhof forest per DNA and Cryptoast); either way she was taken away in the van
- case 445: the first of two attempts on the same victim cannot be told apart from the second in any source on file
- case 447: an attempt broken off by third parties (neighbours) rather than by the victim sits awkwardly inside Dodged Attack
- case 448: targeting vector: not stated; the son is described as a wealthy influencer (public profile is the likely fit, not established by any source)
- case 448: targeting vector: not stated; the son is described as a wealthy influencer (public profile is the likely fit, not established by any source)
- case 448: where the father was held overnight is not stated; France 3 says only that he was released the next day and picked up by motorists
- case 448: where the father was held overnight is not stated; France 3 says only that he was released the next day and picked up by motorists
- case 449: a theft carried out as the physical arm of an online social-engineering enterprise has no label of its own
- case 450: remote iCloud tracking of the victim as the trigger for a physical break-in has no label
- case 450: the file does not say whether the wallet was found, so neither a completed theft nor a dodged attempt can be asserted
@@ -930,6 +1058,10 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 463: the cannabis purchase that brought the pair to the ambush point is not covered by any label, and no source says who set the meeting up
- case 464: he was lured to and held at an attacker's own room, which the batch convention files as Kidnapping although nobody was taken anywhere — he came on the invitation and was held where he arrived
- case 464: the record's single scenario field cannot carry both the lure and the confinement
- case 465: a getaway driver who never entered the villa has no role field
- case 465: a getaway driver who never entered the villa has no role field
- case 465: most of the detail rests on a model transcription of a Facebook post, not on byte-verified text
- case 465: most of the detail rests on a model transcription of a Facebook post, not on byte-verified text
- case 465: the only source is two sentences inside a round-up about a different case (464), so most of the record's detail has nothing behind it
- case 466: the place of detention is never stated in any source, so venue_of_control cannot be filled
- case 466: the record's date is the arrival and abduction, while the deaths were discovered four days later
@@ -942,8 +1074,14 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 474: the ringleader directing from a distance and recruiting through encrypted messaging has no field
- case 475: the exchange's duress detection ending the theft mid-crime has no field
- case 475: the victim's amnesia means the file cannot say how long he was held or exactly what was done
- case 476: targeting vector: lure by telephone; how Glushko knew the victim is not stated
- case 476: targeting vector: lure by telephone; how Glushko knew the victim is not stated
- case 476: the decoy role (the man who makes the call and stays away from the ambush) has no field
- case 476: the decoy role (the man who makes the call and stays away from the ambush) has no field
- case 476: the decoy role - a man who makes the call and is deliberately absent from the ambush - has no field
- case 476: the victim was lured to and held at premises the attackers controlled rather than taken there by force, so Kidnapping is applied by the file's convention for that pattern and the gap is noted here
- case 476: the victim was lured to and held at premises the attackers controlled, and was not taken there by force, so Kidnapping is applied by the file's convention for that pattern and the gap is noted here
- case 476: the victim was lured to and held at premises the attackers controlled, and was not taken there by force, so Kidnapping is applied by the file's convention for that pattern and the gap is noted here
- case 477: no label distinguishes a case where the detention began at home and ended with the victims abandoned kilometres apart
- case 477: the two victims were separated and left in different places, which neither label expresses
- case 478: a young child present through the whole detention has no field of its own
@@ -964,6 +1102,10 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 484: the sequence cannot show that the violence and the gasoline continued after it was clear there was no crypto to take
- case 484: the target was chosen for holdings he did not have, and no field records an attack built on a wrong guess
- case 485: the case is entangled with an exchange collapse, a second missing executive and 4,500 BTC of disputed reserves, none of which an attack label expresses
- case 485: the case is entangled with the Zondacrypto collapse, a second missing executive, 4,500 BTC of disputed reserves and 2026 charges over taking over the missing man's assets, none of which an attack label expresses
- case 485: the case is entangled with the Zondacrypto collapse, a second missing executive, 4,500 BTC of disputed reserves and 2026 charges over taking over the missing man's assets, none of which an attack label expresses
- case 485: there is no outcome value for a victim never found and not declared dead
- case 485: there is no outcome value for a victim never found and not declared dead
- case 485: there is no outcome value for a victim who was never found and has not been declared dead
- case 486: a victim who escaped from a robbery that had already succeeded has no outcome that fits cleanly
- case 487: nothing records how the pair got free after the attackers fled
@@ -998,9 +1140,9 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
## Cases to decide on scope, merge or split
No scenario label fits (mostly empty premises, unattended machines and burglaries with nobody present) — decide whether a physical-attack database keeps them: [3, 6, 10, 21, 24, 57, 62, 99, 101, 105, 112, 195, 198, 349, 383, 409, 449, 450, 468]
No scenario label fits (mostly empty premises, unattended machines and burglaries with nobody present) — decide whether a physical-attack database keeps them: [3, 6, 10, 21, 24, 57, 62, 99, 101, 105, 112, 195, 198, 349, 383, 449, 450]
Writer questioned scope for another reason (not crypto-related, lawful entry, doxing only, argument during a sale, non-violent device theft): [5, 21, 24, 45, 58, 70, 122, 123, 173, 195, 383, 400, 435, 483]
Writer questioned scope for another reason (not crypto-related, lawful entry, doxing only, argument during a sale, non-violent device theft): [5, 21, 24, 45, 58, 70, 122, 123, 173, 195, 383, 400, 435, 483, 485]
Possible merges or splits (same incident across records, or several incidents on one record): [38, 89, 255, 318, 398, 439, 440, 441, 445, 446, 457, 459, 492]