Archived
chore: final state before the move to gart/gart-databases
Commits the work done since 2026-10-01 that was still local: the four-step label and flag passes, the triage and recheck files, the v1 exports of 2026-10-06 and 2026-10-07, the split dossiers, and the Lopp PR 234 batch (scripts, agent prompts, reader and checker files, the flag re-read of 2026-10-17, the review workbook and the import set of the 57 cases added to stats2 as 506 to 562). Raw HTML and node_modules stay out (.gitignore). The stats2 material in use was copied to gart/gart-databases (stats2/) on 2026-10-17; README-START-HERE.md now says so. This repo is closed.
This commit is contained in:
@@ -1,5 +1,7 @@
|
||||
# Definitions — canonical glossary for the K&R database
|
||||
|
||||
> **Scope (owner, 2026-10-16):** this file is the glossary of the February 2026 paper and stays as that paper's record. It is not the definition set of stats2 or of the 2026 AI-crypto report. stats2, the leak record and the AI-crypto report work from the same material: the stats2 `labels` table, `LABEL-RULES.md`, `FLAG-RULES.md` (yes = it occurred, no = it surely did not, empty = unknown, unconfirmed = alleged or disputed) and the leak record's vocabulary. The glossary below uses the paper's single-scenario structure, which stats2 replaced with four steps on 2026-10-06.
|
||||
|
||||
Source of truth: GART Research, "Physical Attacks on Cryptocurrency Holders", research paper v5
|
||||
FINAL (February 2026), Appendix B: Glossary. Copied verbatim below on 2026-09-07 from
|
||||
`03-research-and-publishing/GART Research Crypto K&R Paper /research-paper-v5-FINAL-February-2026.md`.
|
||||
@@ -116,3 +118,16 @@ The official sense of express kidnapping applies (OSAC: "almost always crimes of
|
||||
- **Kidnapping**: everything else: a pre-selected victim (surveillance, a tip-off, a lure, a staged meeting), or a victim taken to a place away from the public where the attackers hold them (a building or a remote outdoor spot), or transported over a long distance, or a ransom demanded from third parties, whatever the duration.
|
||||
|
||||
Duration and the size of the sum do not decide the label. When the sources say nothing about how the victim was chosen, the case stays Express Kidnapping and the gap is noted. Applied 2026-10-01: 91, 279, 334, 182, 202, 137, 462, 456, 80, 19 and 367 moved from Express Kidnapping to Kidnapping; 229, 253, 34, 434, 394, 357, 172 and 7 stay Express Kidnapping.
|
||||
|
||||
## Burglary: twelfth scenario (owner ruling, 2026-10-06)
|
||||
|
||||
Not in the paper's Appendix B glossary, which has eleven scenarios. Added to this database on the owner's ruling of 2026-10-06; the owner approved the wording the same day.
|
||||
|
||||
**Burglary (Scenario)**: Theft from premises, a machine or an unoccupied home in which no person is confronted.
|
||||
|
||||
Boundaries:
|
||||
- A person threatened or held during the theft makes the case Armed Robbery (staff, clerks, guards: 2, 38, 51, 301) or Home Invasion (occupants of a home).
|
||||
- A failed attempt carries both labels, Burglary → Dodged Attack (54, 71, 158), as other failed attacks do (28: Armed Robbery → Dodged Attack).
|
||||
- Cases: 3, 6, 10, 54, 57, 62, 66, 71, 101, 105, 112, 158, 198 (ATMs and the cash inside them); 21, 349 (mining hardware); 99, 383, 449, 450 (a holder's home, nobody present).
|
||||
|
||||
Proposed with it, not yet ruled (DA): a target attribute on every case (holder, business premises, machine), because business and machine targets also appear under Armed Robbery (2, 38, 51, 78, 102, 164, 298, 301, 352, 361), and a decision on whether Burglary cases count in the headline attack figures.
|
||||
|
||||
Reference in New Issue
Block a user