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:
StellarCrow
2026-10-17 10:47:37 +02:00
parent 0f7a691151
commit 41766c68a2
3196 changed files with 374809 additions and 485 deletions
+167
View File
@@ -0,0 +1,167 @@
# Label tests for the four-step structure (updated 2026-10-16)
One test per label, for the seven step fields of stats2. This file and section 6 of `gart-io/databases/stats2/DB-GUIDE.md` carry the same text; change both together.
Where the rules come from: the research paper's glossary (`DEFINITIONS.md`), the owner's rulings (dated in the text and listed in section 9), and the tests the DA wrote on 2026-10-07 to apply them, which the owner has ruled with since. Items marked **[proposed]** or **[check]** have no owner source yet (no invented definitions: DB-GUIDE.md, rule 3.0).
Changes from the version of 2026-10-07, which this replaces:
- Label names follow the live `labels` table, in sentence case: "P2P trade", "Social engineering: ...", "Authority misuse: ...", "Organised by a relative or partner", "Express kidnapping".
- Who was attacked has "Wrong person or address" and "Bystanders or neighbours" (added 2026-10-15 with `case_people`).
- Outcome Released covers victims found alive with no rescue described (owner, 2026-10-15).
- Any object used as a weapon counts (owner, 2026-10-16).
- The owner's precedents are listed in section 9.
Flags (detention, violence, drugs, weapons, theft, deaths) are in `FLAG-RULES.md`: yes = it occurred, no = it surely did not, empty = unknown, unconfirmed = alleged or disputed and not established (owner, 2026-10-16).
Names below are the exact names in the live `labels` table (2026-10-15 copy). Each label belongs on a case only when the text passes its test.
General rules:
- Every label rests on words in the sources (for existing cases: the verified summary, or the dossier where the summary is silent). Nothing is inferred from what usually happens.
- "Unknown" is right when the texts do not say. It never stands beside another label in the same step.
- Several labels are allowed in targeting, who was attacked, approach, attack and obtained. Outcome and targeting accuracy take one.
- There is no "failed" label. An attack that got nothing after someone was held or hurt takes the outcome that happened to the victim, and obtained says Nothing.
## 1. targeting: how the attackers knew of the victim
| Label | Passes when the text says |
|---|---|
| Data leak | the attackers had the victim's details from a leaked or stolen customer, tax or exchange database. A victim's or police suspicion counts only if the text presents it as the working explanation |
| Public records | legally available records (address or tax registers, company filings) |
| Insider tip-off | someone with inside access passed on holdings or movements: employee, driver, guard, contractor, bank or agency staff, a handler who supplied the target |
| Organised by a relative or partner | a relative or partner of the victim organised or enabled the attack. Not when the victim is a relative of a holder (that is who was attacked) |
| Acquaintance | a friend or social contact took part or pointed the attackers to the victim |
| Business counterparty | the attackers knew the victim from trades, investments, a business or debt dispute, or were clients, investors or partners |
| Public profile | known as a crypto holder: executive, founder, influencer, streamer, interviewed or listed as wealthy |
| Social media | the attack followed specific posts or streams (wealth shown, location revealed) |
| Visible wealth | cars, watches, spending or lifestyle seen offline are given as the reason |
| Online contact or advert | the attackers answered the victim's advert, listing or profile on a platform, or first met them through one |
| Surveillance | followed, watched or tracked before the attack. It says how they prepared: add the label for how they first knew the victim when the text gives it |
| Opportunistic | the text shows no prior selection |
| Other | a stated reason that fits none of the above; say which in the evidence |
| Unknown | the texts do not say how the victim was chosen |
Wrong address and assumed wealth are targeting accuracy, never targeting.
## 2. targeting_accuracy (one)
| Label | Passes when |
|---|---|
| Correct | the victim held crypto or assets roughly as sought: crypto taken, transferred, shown, or confirmed as theirs |
| Wealth overestimated | the victim held far less than the attackers believed, or none |
| Wrong person or address | the attackers hit someone other than the intended holder (moved out, previous owner, namesake, wrong flat) |
| Unknown | none of the above is shown. A foiled attack with nothing known about the holdings is Unknown |
## 3. who_was_attacked
| Label | Passes when |
|---|---|
| Holder | the person believed to hold the crypto or assets was confronted, held, hurt or threatened in person, or was the target of a remote attack |
| Relative or partner | a relative or partner was **present at the attack or in the attackers' custody**: confronted, held or hurt in person. A couple or family attacked together is Holder plus Relative or partner |
| Employee or guard | staff of the holder or of a crypto business were confronted, restrained or hurt |
| Wrong person or address | someone attacked in place of the intended holder, usually because the attackers had an outdated address (previous owner or tenant) |
| Bystanders or neighbours | others present who were not family or staff: friends, co-occupants, a neighbour, a passenger, customers in a shop |
| Business premises or machine | a shop, exchange office, mining site or ATM was the target (no people row) |
| Other | anyone the other labels do not cover, or the sources do not say who was attacked |
**Owner's rule (2026-10-07, restated 2026-10-08):** a family member who was not present and not in the attackers' custody was not attacked. A relative who only received the ransom call, negotiated, paid or made the transfer does not count, and a threat spoken to the victim about absent family does not count. Applied to 60, 81, 86, 195, 238.
## 4. approach: how they got to the victim
| Label | Passes when |
|---|---|
| Social engineering: business or investment meeting | drawn to a meeting, trip or call by a business, investment, job or consulting pretext |
| Social engineering: sale / purchase lure | a sale or purchase of something other than crypto (car, property, goods) |
| Social engineering: dating or sexual lure | a romantic or sexual pretext (dating app, a date, a pickup) |
| Social engineering: social invitation | a friend or acquaintance invited them (dinner, party, night out, a visit) |
| Social engineering: pretext at the door | a story told at the door with no claimed role (wrong address, asking for someone, damage to report) |
| Social engineering: other pretext | another deception; say which |
| Social engineering: lure not described | the text says lured or tricked, not how |
| P2P trade | an arranged meeting to exchange crypto or cash, whether or not the other side meant to trade. **Only this label for that meeting**: never add a Social engineering label for it |
| Authority misuse: fake police or official | posed as police, agents, military or officials |
| Authority misuse: serving police or official | serving officers or officials using their position |
| Authority misuse: service ruse (delivery, driver, worker) | posed as delivery, courier, taxi or rideshare driver, technician, worker. **Fake rides and fake deliveries go here only**, never under Social engineering |
| Authority misuse: other claimed role | another claimed role the victim deferred to (client with an appointment, colleague). **[proposed]** also a bank or exchange employee or a concierge: DEFINITIONS.md names them as Authority misuse; the sub-label is the DA's placement |
| Seized in the street or a public place | grabbed or attacked in a street, car park, shop, restaurant or other public place, with no deception |
| Seized at or outside the home | grabbed at the door, gate, garage or building entrance without the attackers entering |
| Taken from the workplace | taken at or from the office or business |
| Vehicle intercepted on the road | the vehicle was blocked, rammed or stopped |
| Walked in | into a shop, exchange office or ATM site open to the public |
| Forced entry | broke or pushed into a home, hotel room, office or shop. A home invasion does not prove it: the text must show force or a break-in |
| Let in by an insider | someone inside opened the door, gave a code or key, or delivered the victim |
| Break-in, nobody present | broke into empty premises |
| Remote, no contact | no physical approach (swatting, threats or extortion from a distance) |
| Unknown | the texts do not say |
Authority misuse (owner, 2026-09-30) covers any real or claimed service position the victim defers to, including a claimed role used only to get a door or gate opened (fake parcel, courier, food delivery, painter, postal or construction uniform) and a police uniform worn on the approach. Reference case: 173 (fake Uber driver, Scottsdale). It is not applied where the file does not show the role being used (397, 434).
## 5. attack: what they did
| Label | Passes when |
|---|---|
| Kidnapping | taken away or held at a place the attackers control, **and** pre-selected, or held away from the public, or moved a long distance, or a ransom asked of third parties. Also a failed attempt at this |
| Express kidnapping | **all three**: not pre-selected, seized in public, made to pay from own funds on the spot or in a vehicle. If the text says nothing on how the victim was chosen and the other two hold, Express kidnapping stands (note the gap) |
| Home invasion | occupants confronted or held in their own home, hotel room or office. Also an attempt at the home |
| Armed robbery | theft or attempted theft by force with a weapon reported, without extended holding. Any object used as a weapon counts (owner, 2026-10-16: cars, a Toblerone bar in case 64) |
| Robbery without a weapon | theft or attempted theft by force or assault, no weapon reported (fists and restraints are not weapons) |
| Mugging | an opportunistic street robbery |
| Burglary | theft from premises, a machine or an empty home with nobody confronted (owner, 2026-10-06). A person threatened or held makes it Armed robbery (staff) or Home invasion (occupants) |
| Extortion without detention | demands backed by threats, in person or remote, nobody held |
| Theft by deception | assets taken by trickery or drugging, no force |
| Swatting | a false emergency report sent armed police to the victim |
| No label fits | none of the above; raise an admin point |
A foiled or fought-off attempt carries the label of the attack that was attempted. Duration and the size of the sum do not decide Kidnapping versus Express kidnapping (owner, 2026-10-01).
## 6. outcome (one)
| Label | Passes when |
|---|---|
| Foiled | stopped before the attackers had anyone under control and without a physical fight: arrested beforehand, plan uncovered, door not opened, an alarm or third party interrupting, theft interrupted with nobody confronted. **An attack that got nothing after holding or hurting someone is not foiled** |
| Fought off | the victim, or someone with them, resisted physically (struggled, hit back, bit, shot) and the attackers gave up and fled, also after briefly holding the victim |
| Escaped | the victim got away by their own action (ran, jumped, slipped out, drove off). The victim left; the attackers did not flee |
| Rescued | freed by police or other people, or the attackers fled because someone else arrived. **Only when the sources describe a rescue** |
| Released | the attackers let the victim go or left of their own accord, including when the victim refused and they ran, or left the victim tied up. **Owner's rule (2026-10-15): abducted victims later found alive, with no rescue described, are Released** (being found means the attackers abandoned them). Do not raise Rescued as an alternative |
| Killed | the victim died as a result of the attack. A later death not linked to it does not count |
| Nobody held or hurt | burglary, swatting or remote cases where no person was confronted |
| Unknown | the texts do not say how it ended |
## 7. obtained: what the attackers got
| Label | Passes when |
|---|---|
| Crypto | cryptocurrency transferred or taken |
| Cash | banknotes or bank money (transfers, withdrawals) |
| Devices or seed | phones, computers, hardware wallets, seed phrases |
| Valuables | watches, jewellery, cars, mining machines, an ATM, other goods |
| Nothing | the text shows nothing was taken. Stands alone |
| Unconfirmed | a taking is alleged or charged and not established, or the sources disagree. Stands alone |
| Unknown | the sources do not say what, if anything, the attackers got. Stands alone (added 2026-10-17 on the owner's decision, so that unknown and unconfirmed stay apart, as for the flags) |
## 8. Changing the vocabulary
New labels, renames and definitions are the owner's decision. To propose one, give the label, the step, a one-line test and the cases it would apply to. Once approved, it goes in by SQL (section 10).
## 9. Owner rulings that work as precedent
Apply these without asking. The full record is `DB-cleanup/merge-output/step-rulings.json`, `corrections-approved.md` and `closed-by-precedent.json`.
| Rule | Cases |
|---|---|
| Absent relatives were not attacked (6.3) | 60, 81, 86, 195, 238 |
| Found alive, no rescue described: Released | 477, 174, 392 |
| A crypto trade meeting is P2P trade only | standing |
| Fake rides and fake deliveries are Authority misuse: service ruse only | standing |
| A claimed service role, or a uniform used only to get in, is Authority misuse | 173 and 29 others |
| Express kidnapping needs all three conditions; everything else is Kidnapping | 91, 279, 334, 182, 202, 137, 462, 456, 80, 19, 367 moved; 229, 253, 34, 434, 394, 357, 172, 7 stayed |
| Burglary: nobody confronted; a failed attempt is Burglary plus outcome Foiled | 3, 6, 10, 54, 57, 62, 66, 71, 101, 105, 112, 158, 198, 21, 349, 99, 383, 449, 450 |
| A weapon found later and never shown to the victims: weapons no | 72, 233, 421, 426, 447, 472 |
| The victim got away and was never held: Escaped; "failed" is not a value | 52 |
| Theft interrupted with nobody confronted: Foiled | 54 |
| The attackers fled because the husband shot at them: Fought off | 218 |
| A knife attack in the street that the victim fought off: Armed robbery, Fought off | 222 |
| Same incident reported twice: merge into the earlier record | 386 into 295, 446 into 445, 440 and 441 into 439, 365 into 323, 296 into 290 |
| One record that holds two attacks: split | 38 (into 38 and 504), 49 (into 49 and 505) |
| Sources are not chased for existing cases; an unconfirmed record detail stays | 235, 231 |