Sofia/DB-cleanup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Activity

docs(detention): forced-entry rule; close the ten open flag items

Browse Source 
Owner's decisions of 2026-09-07 applied:
- Rule sharpened in README "Definitions": forced entry into the victim's
  space (home, office, hotel room, car) followed by beating or holding them
  there to take what is wanted is detention, however short.
- 354, 355 (null) and 124 set to 0. 242, 273, 413, 422, 423, 215, 298 stay 1;
  the set-to-0 proposals for them are withdrawn under the rule.
- corrections-approved.md, detention-flag-review.md and the corrections JSON
  carry the decisions; the worklist item says no open items remain.
- Summaries 242 and 273 relabelled "Detention" with the forced-entry wording.

verify_all.py PASSES.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GZZENdTLzNGsbNy4DyF1yt
This commit is contained in:
StellarCrow
2026-09-07 06:00:54 +02:00
co-authored by Claude Fable 5.1
parent 439e83a4cb
commit de707f8751
9 changed files with 66 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
merge-output/corrections-approved.md
+4 -2
View File
@@ -87,5 +87,7 @@ Rule clarified the same day: detention used on anyone (guards, staff, a concierg
force submission or execute the theft counts as 1, whether or not the record's named victim was
present. Case 301 (guards tied up) is therefore in the list above.
Still open, not yet decided: the 1-to-0 proposals (124, 242, 273, 413, 422, 423, and nulls 354, 355)
and the two CHECK items (215, 298).
→ **Set `kidnappings` to 0 on 354, 355 (currently null) and 124** (decided 2026-09-07).
Withdrawn 2026-09-07, these stay 1: 242, 273, 413, 422, 423, 215, 298. Rule: forced entry into the
victim's space followed by beating or holding them there is detention, however short. No open items.