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

2.2 KiB

Night-shift triage, second reader: confirm or reject each change

A first reader settled open items by precedent. You judge every decision with "action": "apply": only confirmed changes reach the database. You also spot-check the close decisions.

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

Files

  • triage/READER-PROMPT.md: the first reader's instructions and the precedent list. Read it first, then FLAG-RULES.md.
  • triage/in-NN.json: the cases with their open items, record values, summary and dossier path.
  • triage/out-NN.json: the first reader's decisions. Do not change it.
  • corrections-approved.md: the rulings; search DB id <n>.
  • Write triage/check-NN.json. Write nothing else. Read files with the Read tool; never open saved tool-output copies under /home/disi/.claude or /tmp. Fetch nothing from the web. Run no git commands.

What to do

  1. For every apply: confirm only if all hold. The precedent named really covers the item. Every fact in the new value is in the ruling passage, the summary or the dossier (open the dossier when the value states a date, an amount, a name or a place). The value loses no fact the old value had that a source supports. For a flag, the value passes its test in FLAG-RULES.md. The text is plain, with no em dash or en dash. Otherwise reject with a reason.
  2. For every close: reject only when the item plainly orders a concrete change the structure can hold and a precedent covers it, or when it is a split, merge, deletion or policy question that should have been parked. Leave the others alone (no entry needed).

When unsure about an apply, reject: the item then goes to the owner's morning list.

Output

A JSON array: one object per apply, plus one per close you reject.

{"key": "cd34...", "verdict": "confirm"}
{"key": "ef56...", "verdict": "reject", "reason": "the dossier dates it to 14 May, not 15"}
{"key": "0a9b...", "verdict": "reopen", "reason": "orders a split; must be parked"}

An empty array is valid. Valid JSON, straight quotes.

When you finish

Reply with one line: batch, confirmed, rejected, reopened. No victim names in the reply.