# Field pass, second reader: confirm or reject each change A first reader turned written rulings into field changes. You decide, change by change, whether the ruling text supports it. Only confirmed changes are applied to the database build. Working directory: `~/Documents/Claude/GART/03-research-and-publishing/DB-cleanup/merge-output` ## Files - `fields/READER-PROMPT.md`: the first reader's rules. Read it first. - `fields/in-NN.json`: the cases, each with its `record` and `rulings`. - `fields/out-NN.json`: the first reader's result. Do not change it. - Write your verdicts to `fields/check-NN.json`. Write nothing else. Read the files with the Read tool; do not open any saved tool-output copy. ## What to do For every change in every case, read all ruling lines of that case and answer: does the latest ruling on this field order exactly this new value? Confirm when the new value says what the ruling says, in the right field, with nothing added and nothing dropped that the ruling kept. Reject when the value adds a fact the ruling does not state, loses part of the old value that the ruling did not remove, follows an earlier ruling that a later one overrides, applies a pending or parked line, uses the wrong field, or has the wrong date format. Then look once more at each case's rulings for a change to one of the ten fields that the first reader missed. ## Output A JSON array with one object per change, plus one object per missed change: ```json {"id": 176, "field": "location", "verdict": "confirm"} {"id": 23, "field": "date", "verdict": "reject", "reason": "the later ruling sets 2 September, the change uses 1 September"} {"id": 12, "field": "coin_type", "verdict": "missed", "proposed": "Zcash and Monero", "quote": "coin_type → Zcash and Monero", "reason": "ruled and absent from the changes"} ``` `verdict` is `confirm`, `reject` or `missed`. A reject needs a reason. A missed change needs the proposed value, the exact ruling passage and a reason; it is listed for a person and not applied. Be strict: when unsure, reject. Valid JSON, straight quotes. ## When you finish Reply with one line: the batch number, changes confirmed, changes rejected, changes missed.