Archived
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.
53 lines
3.7 KiB
Markdown
53 lines
3.7 KiB
Markdown
# Field pass: turn written rulings into field values
|
|
|
|
Each case in your batch has a database record and one or more ruling lines. A ruling is a decision, by the owner or by the DA under the owner's rules, on what a field of the record should say. Your job is to turn the rulings into exact field changes. You add no facts: every new value must come from the wording of a ruling line.
|
|
|
|
Working directory: `~/Documents/Claude/GART/03-research-and-publishing/DB-cleanup/merge-output`
|
|
|
|
## Files
|
|
|
|
- `fields/in-NN.json`: your batch. Per case: `id`, `record` (the current value of each field you may change) and `rulings` (the ruling lines, oldest first, copied word for word).
|
|
- Write your result to `fields/out-NN.json`. Write nothing else. Read the batch with the Read tool; do not open any saved tool-output copy.
|
|
|
|
## Output
|
|
|
|
A JSON array, one object per case in the batch, same order:
|
|
|
|
```json
|
|
{
|
|
"id": 176,
|
|
"changes": [
|
|
{"field": "location", "expected_old": "Singapore", "new": "King Albert Park, Singapore", "quote": "location → King Albert Park, Singapore (residential unit)"}
|
|
],
|
|
"not_applied": [
|
|
{"quote": "details requested on the date", "reason": "the ruling asks for more information and sets no value"}
|
|
]
|
|
}
|
|
```
|
|
|
|
A case with nothing to change has `"changes": []`.
|
|
|
|
## Rules
|
|
|
|
1. **Fields you may change:** date, victim, location, country, description, notes, money_wanted, coin_type, reports, arrests. Nothing else.
|
|
2. **Ignore** what other files already carry: scenario or sequence changes, the flags (kidnappings or detention, violence_torture, drugs_alcohol, weapons, theft, life_taken), the targeting vector, venue, held duration, outcome. Do not list these under `not_applied` either.
|
|
3. **`expected_old`** is the record's current value, copied exactly from `record`.
|
|
4. **`quote`** is copied exactly from one ruling line: the shortest passage that states the change. A script checks that it appears word for word in the ruling text, so do not paraphrase, trim inside it or join two passages.
|
|
5. **`new`** is the full new value of the field, ready to store, in the record's own style:
|
|
- `date`: "Month D, YYYY" (for example "November 3, 2015"). Month only: "April, 2017". A span of days: "May 10 to 11, 2026". Use what the ruling gives and no more precision than it gives.
|
|
- `victim`, `location`, `country`: short, as the existing records write them.
|
|
- `description`: one or two plain sentences. Change only what the ruling says and keep the rest of the existing description. Where a ruling replaces the description, write the replacement from the ruling's wording.
|
|
- `notes`: the existing note with the ruled change made, or the ruled text added.
|
|
- `money_wanted`, `coin_type`: as the ruling states them.
|
|
- `arrests`: one of none, some, all, convicted.
|
|
6. **The later ruling wins.** Where two lines disagree, apply the later one and quote it.
|
|
7. **Do not apply** a line marked pending, parked, proposed, "details requested", "owner to confirm" or similar, or a value the ruling itself calls uncertain without choosing one. Put it under `not_applied` with the passage and a short reason. Do the same when a ruling clearly orders a change that fits none of the ten fields and is not covered by rule 2 (for example "merge with case 441", "split into two records", "add the Yahoo article to the links").
|
|
8. A ruling that says a field "stays", is "kept" or is "unsupported on file (keep)" is no change.
|
|
9. If the record already holds the ruled value, there is no change.
|
|
10. Do not use the victim's name for case 184; write "the victim" there.
|
|
11. Straight quotes in your own text, no em dashes in `new` values, valid JSON. Check your file parses before you finish.
|
|
|
|
## When you finish
|
|
|
|
Reply with one line: the batch number, cases written, total changes, total not_applied.
|