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/recheck/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

4.6 KiB

Recheck of two fields: who was attacked, and the outcome "fought off"

The owner of the Gart database of attacks on crypto holders found two faults in the current data and ordered a recheck of every case. You read each case's verified summary and give the correct value of two fields. You add no facts: every change must be supported by words in the summary.

Working directory: ~/Documents/Claude/GART/03-research-and-publishing/DB-cleanup/merge-output

Files

  • recheck/in-NN.json: your batch. Per case: id, victim_field (the record's title), current (the two values as they stand), attack, detention and the verified summary.
  • step-labels.json: the label lists. Read the entries who_was_attacked and outcome.
  • Write your result to recheck/out-NN.json. Write nothing else. Read files with the Read tool; do not open any saved tool-output copy.

Field 1: who_was_attacked (several values allowed)

Every kind of person or thing the attackers confronted, held, hurt or threatened:

  • holder: the person believed to hold the crypto or assets.
  • relative or partner: spouse, partner, child, parent or other family of the holder, when they were attacked, held or threatened too, used as leverage, or attacked in the holder's place.
  • employee or guard: staff of the holder or of a crypto business (driver, bodyguard, concierge, clerk).
  • business premises or machine: a shop, exchange office, mining site or ATM was the target.
  • other: anyone else attacked (friend, bystander, neighbour, business partner present).

The fault to correct: many cases say only holder although the summary shows more people attacked.

  • A couple, or a family, attacked together is holder plus relative or partner. This holds when the summary does not say which of them holds the crypto.
  • Children, parents or a partner held, tied, threatened or hurt during an attack on the holder: add relative or partner.
  • A relative merely present and untouched, or merely mentioned, does not count.
  • When only a relative was attacked and the holder was absent, the value is relative or partner alone.
  • Staff restrained or threatened: add employee or guard. Friends or companions attacked with the victim: add other.
  • Do not remove a current value unless the summary plainly contradicts it.

Field 2: outcome (one value)

The list is: foiled, escaped, fought off, rescued, released, killed, nobody held or hurt, unknown. fought off is new. Check whether the case belongs to it:

  • fought off: the victim, or someone with them, resisted physically (struggled, hit back, bit, wrestled, drew a weapon in defence) and the attackers gave up and fled. It also applies when the victim was briefly held or threatened first.
  • escaped: the victim got away from the attackers by their own action (ran, jumped, slipped out, drove off). The victim left; the attackers did not flee.
  • foiled: stopped before the attackers had anyone under their control and without a physical fight with the victim (arrested beforehand, turned away, the plan uncovered, the door not opened, an alarm or a third party interrupting).
  • released: the attackers let the victim go or left of their own accord, including when the victim simply refused and they ran.
  • rescued: freed by police or other people.
  • killed: the victim died.
  • nobody held or hurt: burglary, swatting, remote cases.
  • unknown: the summary does not say how it ended.

There is no value "failed". Change the outcome only where the summary supports another value better than the current one; the main purpose is to find the fought off cases. If the victim died, the outcome is killed whatever else happened.

Output

A JSON array, one object per case in the batch, same order:

{"id": 123, "who_was_attacked": ["holder", "relative or partner"], "who_evidence": "tied up the couple and their two children", "outcome": "fought off", "outcome_evidence": "bit through the man's index finger"}
  • Give both fields for every case, changed or not.
  • who_evidence and outcome_evidence are required when your value differs from current. Each must be copied word for word from the summary: one continuous passage, the shortest that shows it. A script checks that it appears in the summary exactly, so do not paraphrase, shorten inside it or join two passages. When the value is unchanged, the evidence may be an empty string.
  • Straight quotes, valid JSON. Check your file parses before you finish.

When you finish

Reply with one line: the batch number, cases written, how many who_was_attacked values changed, how many outcomes changed, and the ids changed to fought off.