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/batches/COMPARE-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

28 lines
3.3 KiB
Markdown

# Field comparison: record against articles, for cases whose summary is already verified
You are verifying cases of the Gart K&R crypto-attack database. Work ONLY inside
/home/disi/Documents/Claude/GART/03-research-and-publishing/DB-cleanup/merge-output
These cases already have a verified summary and scenario sequence. What was never done for them is steps 5, 6 and 7 of the procedure: the flags, the record-versus-article contradictions and the facts. That is your job. You do not rewrite the summary or the sequence.
Read first, in this order:
1. VERIFICATION-PROCEDURE.md (the seven steps and the output schema)
2. DEFINITIONS.md (the six violence categories and the owner's detention rulings)
3. batches/batch-20.json (a finished batch: match the depth of its `flags`, `contradictions`, `facts` and `notes_for_sofia`)
Your input is batches/compare-NN.in.json: per case the `id`, the `dossier` path, and six fields that are already verified: `summary`, `sequence`, `attempted`, `gaps`, `v1_label_supported`, `rationale`.
For each case:
- Open the dossier and read ALL of it with the Read tool: the DATABASE RECORD block, the site's AI SUMMARY (bulk text, unverified, do not trust it), every ARTICLE and FETCHED ARTICLE block in any language, and the OTHER LINKED SOURCES list. Do not use a block marked OFF-CASE, and check auto-trim-review.md for blocks listed as OFF-CASE? for this case. Round-up articles: use only the passage about this case. Never open saved tool-output copies under /home/disi/.claude or /tmp.
- Copy the six verified fields into your output exactly as given, character for character. A script compares them.
- Add:
* `flags`: for each of the six (kidnappings, violence_torture, drugs_alcohol, weapons, theft, life_taken): the record's value (`"null"` when the record has none), `supported` true or false, the `evidence` line quoted from an article, and `proposed` only when unsupported. Detention (the field `kidnappings`) per DEFINITIONS.md.
* `contradictions`: every disagreement between the DATABASE RECORD and the articles on date, location, victim, amount, coin, weapons, detention, violence, drugs, deaths, attackers, arrests, description, notes. Quote the article line and name the source. Do not resolve them. If the verified summary itself disagrees with the articles, log that too with field `"verified summary"`.
* `off_case_links`: links whose article is a different incident, and duplicate links.
* `record_only`: true when no usable article is on file.
* `facts`: venue_of_control (victim's private space | victim's workplace | attacker's or third-party space | vehicle in motion | public space | none), held_duration (none | minutes | hours | days), outcome (released | escaped | rescued | killed | foiled | unharmed), arrests (none | some | all | convicted). Null when the file does not say.
* `notes_for_sofia`: what a person correcting the record should know, in a few sentences.
- No outside knowledge, no guessing. Keep the source's hedges. Non-English articles: read them and write in English.
Write the finished array to batches/batch-NN.json (NN = your batch number) and nothing else. Do not edit any other file. Do not fetch anything from the web. Confirm the file parses as JSON. When done, reply with one line: the batch number, the ids finished, the number of contradictions logged, and any case you could not finish and why.