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/DECISION-RULES.md
T

5.4 KiB

Decision rules for owner-decision triage (2026-10-01)

Owner instruction: approve the cases where the judgment is safe; show the owner only the cases that need human eyes or a decision.

Inputs per case: batches/contradictions-NN.md (record-versus-article disagreements, flag proposals, gap notes, writer's note), batches/batch-NN.json (verified summary, sequence, flags with evidence, facts), sources/<id>_*.txt (the dossier: record block, articles), DEFINITIONS.md (glossary plus owner rulings), corrections-approved.md (every owner ruling so far, the precedent base: read it in full before deciding anything).

Approve without the owner (mark "(DA)")

A correction is safe when the article text on file states it and no owner ruling points the other way:

  • A flag proposed from an explicit quote: detention 1 for restrained, tied, locked in, held at gunpoint, forced into a vehicle or a room; violence 1 for a beating, injury, pepper spray, taser (rulings 160, 89, 84); weapons 1 for a weapon named; theft unconfirmed when no transfer or loss is stated; weapons unconfirmed when "armed" appears only in a charge or headline; drugs 1 as alleged when a source says the victim was drugged.
  • Date, location, victim age or name, attacker count, amount, coin: changed to what the article says, with the article's hedges kept. Convert a weekday to a date only when the report's date fixes it; otherwise "month YYYY, day unknown". Note currency-sign traps (Argentine , HK) and unsourced dollar conversions: keep the source currency, drop or mark the conversion.
  • Description rewritten to the article when the record overstates (e.g. "take millions in bitcoin" when nothing was moved; "armed" with no weapon).
  • Scenario changes that follow a ruling already made:
    • worker, driver, delivery, technician, insurance or official ruse at the door or in the street → Authority Misuse as the first label (ruling of 2026-09-30; cases 118, 90, 114);
    • a crypto trade used as the lure → P2P Trade Gone Wrong in the sequence: after Malicious Invitation when the meeting itself was engineered (117: Malicious Invitation → P2P Trade Gone Wrong), first when the trade was the approach (137, 143, 104);
    • victim held at the attackers' premises, or pre-selected and held in a vehicle → Kidnapping; Express Kidnapping only when not pre-selected, seized in public, paying from own funds on the spot or in a vehicle (rule of 2026-10-01 in DEFINITIONS.md);
    • foiled attempt → Dodged Attack with the attempt listed (147, 84);
    • a man shot or stabbed dead → violence_torture 1 (215, 102, 96);
    • unconscious or drugged, not held → kidnappings 0 (151, 124, 88);
    • "injury" in a conviction after a drugging → violence unconfirmed (88).
  • Targeting vector noted (insider, acquaintance, business counterparty, surveillance, tip-off, leak from the victim's circle, displayed wealth, opportunistic, unknown).
  • Source housekeeping: an OFF-CASE? flag that is a matcher artefact (the record's victim string never appears in a foreign-language page) is noted as "article is the right one"; round-up tails not used.

Escalate to the owner (mark "(owner)")

  • A scenario change with no precedent in corrections-approved.md, or a case that fits none of the eleven labels (park on the disputed list if it is an empty-premises theft: ATM, mining hardware, burglary of an empty home; otherwise escalate).
  • Detention on the line between "held to execute the theft" and "a snatch in passing" (clarification 3) when the hold is more than a grab.
  • Whether the case belongs in the database at all (no crypto link, motive not established, no person attacked, lawful police action).
  • Two sources that disagree on a central fact (amount, who the attackers were, whether the victim was released) and the record must pick one.
  • Anything that would need a new source to settle, and the writer's note says the record's details are in no source on file (as in 145, 138, 114: trace first).
  • A record whose description is a different incident from the article (possible off-case link).
  • A possible duplicate of another record, or an article describing further incidents that may deserve their own records (list them; do not create records).
  • Victim named in the record but not in any source: approve the removal of the name only if no source names the person; escalate if a source names someone else.

Output

One file per batch: batches/decisions-NN.md, two sections.

## Approved (DA): one line per case in the exact format of corrections-approved.md: - **DB id N** (DA) — field → value (evidence); ...; sequence A → B (reason); flags unchanged (list); arrests; source notes. Write "sequence X kept" when unchanged; "sequence was A; now B" when changed. Keep every claim traceable to the article text or a prior ruling.

## Needs owner decision: one block per case, at most eight lines: a one-line TL;DR of the case, what is settled (DA), and the one or two questions for the owner with the evidence line for each side and the DA's recommendation.

Also write batches/decisions-NN.json: {"sequence_changes": {"<id>": ["label", ...]}, "attempted_changes": {"<id>": [...]}, "parked": [ids], "owner": [ids]} listing only the cases whose sequence or attempted list changes under the approved decisions.

Do not edit corrections-approved.md, scenario-sequences.json, summary-overrides.json, DEFINITIONS.md or anything in sources/. Do not fetch anything from the web. Never invent a fact: if the file does not say it, write "not stated".