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/triage/READER-PROMPT.md
T
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

6.0 KiB

Night-shift triage of open items, first reader

The owner of this database of physical attacks on crypto holders is away and has ordered: settle every open item by precedent where earlier rulings cover it, park the rest for one morning list. You decide each open item in your batch.

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

Files

  • triage/in-NN.json: your batch. Per case: id, open_items, record (the values now in the database), the verified summary, the dossier path (full article text).
  • Each open item has key, kind, field, detail (why it is open), value_now, value_proposed, quote (the ruling passage or the evidence).
  • LABEL-RULES.md, FLAG-RULES.md: the written tests. Read both first.
  • corrections-approved.md: every ruling so far. Search it for DB id <n> when you need the full ruling behind an item.
  • Write triage/out-NN.json. Write nothing else. Read files with the Read tool (offset and limit for large files); never open saved tool-output copies under /home/disi/.claude or /tmp. Fetch nothing from the web. Run no git commands.

The structure

The database holds, per case: date, victim, location, country, description, summary, notes (admin only), money_wanted and coin_type (admin only), five flags (detention, violence_torture, drugs_alcohol, weapons, theft), life_taken, and the step labels. It has no field for attackers, arrests, motive or a second record.

Precedents (the owner's rulings; apply them)

  1. No source, no change of fact. A detail in the record that no source on file confirms stays as recorded. The owner does not want new sources chased (ruling on 235: "dont transcribe"; on 231: keep the record's attackers although the one article does not confirm them). An item that only asks for a link to be found, a video transcribed, a fuller extract fetched or a source traced: close, reason "source chase not pursued (owner, 235)".
  2. An item that orders something no field holds (an attackers line, an arrests line, a motive flag, a spelling "noted"): if the ruling gives wording that belongs in the admin notes, apply it as an append to notes; if it gives nothing to write, close, reason "no field in this structure".
  3. A ruling that gives a concrete new value for date, victim, location, country, description, money_wanted or coin_type, and was left unapplied only for a formal reason (second reader disliked the wording, first reader missed it, pending marker): apply the value the ruling states. Write the full new value of the field. For description, keep it to one or two plain sentences built only from the ruling text and the summary.
  4. Flags follow FLAG-RULES.md and these owner rulings: a weapon found on the attackers or in their car and never shown to the victims is weapons no; threats with no physical violence reported are violence_torture threat only; theft unconfirmed when the text does not say whether anything was taken; drugs unconfirmed when only a suspicion or a pending toxicology exists; a death the police state as their finding counts (life_taken a number), also without a body.
  5. A relative who was not present and not in custody was not attacked. There is no "failed attack": an attack stopped before anyone was under control is foiled; victims who drove the attackers off are fought off.
  6. A label change two of three readers turned down stays turned down: close, reason "decided by two of three readers".
  7. Amount disputes (demanded, taken): if the summary states the amount plainly, close with the reason; the amount fields are not yours to set. If the readers differ on a real ambiguity, park.
  8. Splits of a record, new records, merges, deletions, removing a case from the database: always park. So is anything that needs a decision of taste or policy no ruling covers.

When a precedent covers the item, do not park it. When none does, park it and say which decision is missing.

Output

A JSON array with one object per open item (every key in your batch, none skipped):

{"key": "ab12...", "id": 123, "action": "close", "reason": "source chase not pursued (owner, 235)"}
{"key": "cd34...", "id": 123, "action": "apply", "change": {"field": "notes", "op": "append", "value": "Attackers: two men inside, two more waiting in a red Chevrolet Cavalier (police account)."}, "quote": "exact passage from the item's quote, the summary or the dossier that supports the value", "precedent": "2", "reason": "attackers line has no field; ruling wording goes to notes"}
{"key": "ef56...", "id": 124, "action": "apply", "change": {"field": "weapons", "op": "set", "value": "no"}, "quote": "...", "precedent": "4", "reason": "..."}
{"key": "0a9b...", "id": 125, "action": "park", "reason": "whether the pickpocketing belongs in the database", "options": "keep as one record | split in three", "default": "keep as one record"}

Rules for apply:

  • field is one of date, victim, location, country, description, money_wanted, coin_type (op set, full new value), notes (op append, the sentence to add), a flag (op set; yes, no, unconfirmed, or threat only for violence_torture) or life_taken (op set; a number as a string, or unconfirmed).
  • At most one set per field per case. If two items of one case touch the same field, write one combined value on the first and close the second with the reason "covered by the change on key ...".
  • quote: one contiguous passage, at least 8 characters, copied character for character from the item's quote or detail, the summary or the dossier.
  • Every fact in a new value comes from the ruling or the sources. Invent nothing. Plain English, straight quotes, no em dash or en dash (use commas, colons, "to"), dates like "March 24, 2025" or "May ?, 2021" or "2021" in the date field (the forms the database already uses; look at record.date).
  • Park needs options and a recommended default.

When you finish

Check the file parses and has one object per open item. Reply with one line: batch, items, applied, closed, parked. No victim names in the reply.