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

36 lines
2.2 KiB
Markdown

# Recheck, second reader: confirm or reject each change
A first reader rechecked two fields on every case: `who_was_attacked` and `outcome` (with the new value `fought off`). You judge every value the first reader changed. Only confirmed changes reach the database.
Working directory: `~/Documents/Claude/GART/03-research-and-publishing/DB-cleanup/merge-output`
## Files
- `recheck/READER-PROMPT.md`: the rules. Read it first.
- `recheck/in-NN.json`: the cases with their summaries and `current` values.
- `recheck/out-NN.json`: the first reader's result. Do not change it.
- Write your verdicts to `recheck/check-NN.json`. Write nothing else. Read files with the Read tool; do not open any saved tool-output copy.
## What to do
1. For every case where the first reader's `who_was_attacked` or `outcome` differs from `current`, read the summary and decide: does the summary support the new value under the rules? Confirm or reject. Order of values in a list does not matter.
2. Then go through every case once more for what the first reader missed: a couple, family, staff member or companion who was attacked and is absent from `who_was_attacked`; a case where the victim fought the attackers off and the outcome says something else.
Reject when the new value rests on someone merely present or mentioned, removes a value the summary supports, calls an outcome `fought off` where the victim did not resist physically or the attackers did not flee because of it, or contradicts a death (`killed` wins).
## Output
A JSON array: one object per changed field, plus one per missed change.
```json
{"id": 123, "field": "who_was_attacked", "verdict": "confirm"}
{"id": 77, "field": "outcome", "verdict": "reject", "reason": "she was found locked in by police, which is rescued"}
{"id": 301, "field": "who_was_attacked", "verdict": "missed", "proposed": ["holder", "employee or guard"], "quote": "tied up the two clerks", "reason": "staff restrained, not in the list"}
```
A reject needs a reason. A missed change needs the proposed value, an exact passage from the summary and a reason; it is listed for a person and not applied. When unsure, reject. Valid JSON, straight quotes.
## When you finish
Reply with one line: the batch number, changes confirmed, rejected, missed.