This repository has been archived on 2026-10-19. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
DB-cleanup/merge-output/relatives/READER-PROMPT.md
StellarCrow 41766c68a2 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.
2026-10-17 10:47:37 +02:00

2.1 KiB

Relatives check: was a family member present or in custody?

The owner's rule: a family member who was not present at the attack 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. A threat spoken to the victim about absent family does not count.

Every case in your batch carries the label relative or partner in who_was_attacked. Decide for each whether the label stays.

Working directory: ~/Documents/Claude/GART/03-research-and-publishing/DB-cleanup/merge-output. Read LABEL-RULES.md section 1c first. Input relatives/in-NN.json (id, who_was_attacked, summary, dossier path). Read files with the Read tool only; never open saved tool-output copies under /home/disi/.claude or /tmp. Fetch nothing from the web, run no git commands, write only your output file.

  • keep: a relative was present at the attack or held by the attackers: in the home during the invasion, abducted, tied up, hurt, threatened in person. A relative who IS the person seized (the wife, child or parent of the crypto holder taken for ransom) is in custody: keep.
  • remove: the only role of any relative was to receive the demand, negotiate, pay, transfer, report to police, or be named in a threat while absent.
  • Open the dossier when the summary does not settle it. When the text does not say whether the relative was present, keep and say so in the reason.

For a remove, give the new full value of who_was_attacked: the current list without relative or partner. If that leaves the list empty, decide who was attacked by the tests in section 1c (usually holder) and say why.

Output relatives/out-NN.json: a JSON array, one object per case in input order: {"id": 81, "verdict": "remove", "value": ["holder"], "quote": "exact passage from the summary or dossier showing the relative's role", "reason": "one sentence"} {"id": 12, "verdict": "keep", "reason": "wife tied up in the home"} A remove needs a quote copied character for character, at least 8 characters. Valid JSON. Reply with one line: batch, kept, removed, and the ids removed. No victim names in the reply.