feat(verify): owner rulings on triage groups C-E; 7 sequences set (15, 18, 406, 11, 399, 468, 397)

This commit is contained in:
StellarCrow
2026-10-01 12:17:14 +02:00
parent e2785f8c7f
commit 25a2db3ded
2 changed files with 62 additions and 14 deletions
+40
View File
@@ -619,3 +619,43 @@ Approved by the DA under `batches/DECISION-RULES.md`; evidence in `batches/contr
- **DB id 63** (owner) — keep in the database as is (crypto exchange accounts forced open to launder the cash).
- **DB id 376** (owner) — keep, tagged "crypto as extraction rail" (ransom paid through a crypto account; no holder targeted).
- **DB id 56** (owner) — keep; sequence Home Invasion (tortured for his password in his rented house); targeting vector = business counterparty.
## Owner rulings on the triage escalations — 2026-10-01 (part 2: merges, labels, flags)
Merges, splits, deletions (database operations for the worklist):
- **DB id 386** (owner) — delete as a duplicate of 295 (same John Forsyth incident, February 2022); move its sources (Fox News, Daily Mail) to 295.
- **DB ids 445, 446** (owner) — merge into 445, dated 10 to 11 May 2026 (one operation in all five sources); delete 446.
- **DB ids 439, 440, 441** (owner) — merge into 439 as "three attempts on consecutive days, early March 2026"; delete 440 and 441.
- **DB id 49** (owner) — split: this record keeps the 20 May 2018 kidnapping of the boy (Witbank); new record for the 21 August 2018 attempt on the girl (Aerorand, Middelburg), same two suspects.
- **DB id 38** (owner) — split into Irving (22 March 2018) and Mesquite (28 March 2018); both bear-spray ATM robberies with clerks present.
- **DB id 5** (owner) — rewrite to the 27 May 2015 Crown Heights robbery (victim: 28-year-old man, unnamed; CNBC); the Dwayne Richards stabbing (February 2015, Observer) leaves this record and gets no record of its own (police called it not bitcoin-related).
- **DB ids 20, 374** (owner) — no new records for the incidents mentioned without detail.
- **DB id 458** (owner) — the Gardanne attack of the same night: find a report online, source it, analyse, summarise and add it to the database (pending research).
- **DB id 430** (owner) — link to 138, 145 and 156 (same crew); no merge.
Labels:
- **DB id 15** (owner) — Malicious Invitation → Kidnapping (held about three hours in a club room, as 194).
- **DB id 46** (owner) — Home Invasion, marked DISPUTED (recanted); drugs_alcohol → 0.
- **DB id 18** (owner) — P2P Trade Gone Wrong alone; one series record.
- **DB id 406** (owner) — Dodged Attack, attempted Home Invasion (struck at the wrong address, no entry).
- **DB id 11** (owner) — P2P Trade Gone Wrong (on the record description; podcast untranscribed).
- **DB id 399** (owner) — P2P Trade Gone Wrong → Kidnapping; sources: the victim's direct report to Gart Research and his later Instagram post https://www.instagram.com/p/DWhihZeGNtC/ (to be put on file).
- **DB id 409** (owner) — details requested for manual validation; until then sequence empty, marked uncorroborated.
- **DB id 468** (owner) — sequence Home Invasion (owner reading; the sources establish no intruder, cause of death undetermined).
- **DB id 54** (owner) — added to disputed group A with 57 and 158.
- **DB id 397** (owner) — Authority Misuse → Kidnapping, applied (The Hindu, on file under 398: posed as Income Tax officials, farm house, three days); supersedes the DEFINITIONS.md note that left 397 out.
- **DB id 483** (owner) — kidnappings → 1, custody noted as lawful.
Flags and facts:
- **DB id 73** (owner) — weapons → 1 if the attackers used the deodorant: Gulf News says they "sprayed a deodorant directly on to the victims' faces", the second report says a victim sprayed the robbers; applied as 1 on Gulf News with the conflicting account in notes.
- **DB id 72** (owner) — weapons → 1 only if the victim saw the tools; the plot was intercepted before contact, so weapons → 0, prepared torture tools in notes.
- **DB id 40** (owner) — weapons → 0 (the only gun was the victim's), theft → unconfirmed.
- **DB id 42** (owner) — kidnappings → 1 (stopped from leaving the rented office by force).
- **DB id 33** (owner) — kidnappings → 1 (held through the assault, the transfer and the forced drinking).
- **DB id 8** (owner) — kidnappings → 1 (knife to the chest in his car, as 241); violence_torture → 1.
- **DB id 438** (owner) — kidnappings stays 1 (clarification 1), note that no holding is described.
- **DB ids 419, 444, 482** (owner) — details requested; pending (419 and 444 also in the source trace).
- **DB id 12** (owner) — money_wanted → R$115 million demanded, reduced to R$5 million, unpaid; coin_type → Zcash and Monero; details requested on the date and the Business Insider death claim before ruling on them.
- **DB id 32** (owner) — trial figures as the amount (176 BTC plus Rs 32 crore demanded; 34 BTC sold, about $150,000 transferred), Bhatt's 2018 allegation in notes; description drops "200 BTC".
- **DB id 381** (owner) — location → Dompierre-sur-Mer near La Rochelle; money_wanted → about 8 million euros in crypto (not $10 million); violence_torture stays 1 (round-up tails under 392, 389, 388, 404); fetch the dedicated report.
- **DB id 223** (owner) — police account via Rappler (seized in Meycauayan, Bulacan; around 200 million pesos paid in crypto), Tulfo column's version noted.
+22 -14
View File
@@ -3790,7 +3790,6 @@
},
"18": {
"sequence": [
"Malicious Invitation - SocialEng",
"P2P Trade Gone Wrong"
],
"attempted": [],
@@ -3800,7 +3799,7 @@
"the infant present during some of the robberies, which drew child-abuse counts, has no field"
],
"v1_label_supported": false,
"rationale": "The file supports a lure and an in-person cash-for-bitcoin meeting used as the robbery, not the record's Armed Robbery in Public Space: no public setting appears anywhere in the file and the initiation was the fake discount-bitcoin advert.",
"rationale": "The file supports a lure and an in-person cash-for-bitcoin meeting used as the robbery, not the record's Armed Robbery in Public Space: no public setting appears anywhere in the file and the initiation was the fake discount-bitcoin advert. Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). Series record; no public place on file.",
"facts": {
"venue_of_control": null,
"held_duration": "none",
@@ -4312,14 +4311,16 @@
"batch": "21"
},
"468": {
"sequence": [],
"sequence": [
"Home Invasion"
],
"attempted": [],
"gaps": [
"an unexplained death of a crypto holder, with a ransacked flat and no established intruder, fits none of the eleven labels",
"the file cannot say whether a crime occurred at all, and the schema has no undetermined state"
],
"v1_label_supported": false,
"rationale": "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 labels fits.",
"rationale": "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 labels fits. Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). Owner reading: flat turned over, death undetermined; sources establish no intruder.",
"facts": {
"venue_of_control": null,
"held_duration": "none",
@@ -4432,7 +4433,8 @@
},
"15": {
"sequence": [
"Malicious Invitation - SocialEng"
"Malicious Invitation - SocialEng",
"Kidnapping"
],
"attempted": [],
"gaps": [
@@ -4440,7 +4442,7 @@
"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"
],
"v1_label_supported": true,
"rationale": "A fake consultation for a supposed investor, rehearsed at a first meeting, drew him to a second meeting where three men ambushed him (Malicious Invitation / Social Engineering); the detention happened at that meeting place.",
"rationale": "A fake consultation for a supposed investor, rehearsed at a first meeting, drew him to a second meeting where three men ambushed him (Malicious Invitation / Social Engineering); the detention happened at that meeting place. Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). Held about three hours in a club room, as 194.",
"facts": {
"venue_of_control": "attacker's or third-party space",
"held_duration": "hours",
@@ -4511,14 +4513,16 @@
"batch": "18"
},
"11": {
"sequence": [],
"sequence": [
"P2P Trade Gone Wrong"
],
"attempted": [],
"gaps": [
"the record's own description — a robbery during a Localbitcoins trade — reads as P2P Trade Gone Wrong, but with no report on file no label can be tested, so none is asserted (same treatment as 45 and 66)",
"there is no way to mark a record whose only source is an untranscribed podcast; only record_only carries it"
],
"v1_label_supported": false,
"rationale": "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.",
"rationale": "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. Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). Rests on the record description (robbery during a Localbitcoins trade); podcast untranscribed.",
"facts": {
"venue_of_control": null,
"held_duration": null,
@@ -5883,14 +5887,17 @@
"batch": "28"
},
"399": {
"sequence": [],
"sequence": [
"P2P Trade Gone Wrong",
"Kidnapping"
],
"attempted": [],
"gaps": [
"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)",
"there is no field for a case whose only source is the victim's own report to Gart Research; record_only carries it but does not distinguish a missing source from a first-hand one"
],
"v1_label_supported": false,
"rationale": "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 record's own description).",
"rationale": "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 record's own description). Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). Victim report direct to Gart Research and his later Instagram post (https://www.instagram.com/p/DWhihZeGNtC/), to be put on file.",
"facts": {
"venue_of_control": null,
"held_duration": null,
@@ -5920,6 +5927,7 @@
},
"397": {
"sequence": [
"Authority Misuse",
"Kidnapping"
],
"attempted": [],
@@ -5928,7 +5936,7 @@
"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"
],
"v1_label_supported": false,
"rationale": "Nothing in this case's file mentions anyone posing as Income Tax officers, so Authority Misuse cannot be tested here; what the two articles support is a kidnapping - taken on 30 January and released two days later, with CoinJournal placing the extortion of the two BitConnect men at gunpoint.",
"rationale": "Nothing in this case's file mentions anyone posing as Income Tax officers, so Authority Misuse cannot be tested here; what the two articles support is a kidnapping - taken on 30 January and released two days later, with CoinJournal placing the extortion of the two BitConnect men at gunpoint. Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). The Hindu article on file under 398 says the attackers posed as Income Tax officials and held him at a farm house for three days.",
"facts": {
"venue_of_control": null,
"held_duration": "days",
@@ -6325,10 +6333,10 @@
},
"406": {
"sequence": [
"Home Invasion"
"Dodged Attack"
],
"attempted": [
"a home-jacking of the crypto holder the men were looking for, whom RTL names only as 'X.'"
"Home Invasion (home-jacking of the intended target X., struck at the wrong address)"
],
"gaps": [
"an attack on the wrong address, against someone with no connection to crypto, has no label",
@@ -6336,7 +6344,7 @@
"one commando and two victims on the same morning are held as two records with no link field between them"
],
"v1_label_supported": true,
"rationale": "Armed hooded men attacked her at her own address while hunting for a crypto holder's house, which makes Home Invasion the closest of the eleven labels, though RTL describes neither an entry nor a holding.",
"rationale": "Armed hooded men attacked her at her own address while hunting for a crypto holder's house, which makes Home Invasion the closest of the eleven labels, though RTL describes neither an entry nor a holding. Set 2026-10-01 by owner ruling on the triage escalations (corrections-approved.md, part 2). No entry or holding described.",
"facts": {
"venue_of_control": "victim's private space",
"held_duration": "none",