Cases: Registration to Execution

Registration

Incoming report context becomes a case record. Reception is a verified staff-assignment example connected to the station’s intake surface.

1. Confirm intakeRecord what report or case you are tracking.
2. Separate known from unknownDo not invent forms, rewards or success conditions.

Examination

Evidence, leads and detective work develop the case. The Detective Board and strategic intelligence are relationships, not a published universal solution path.

1. Review evidenceTrack what the game actually presents.
2. Assign detective workUse current build behavior and official role context.

Execution

Field action or outcome follows examination. Exact intervention, suspect and reward details depend on the current case and product slice.

1. Prepare the field stepConnect to patrol, intervention or arrest context.
2. Record the outcomeA local board move is a note, not game state.

Use the personal board safely

Case labels, people, notes and checklists remain in your browser’s local storage. Export is explicit JSON; invalid imports never replace valid data.

Patch changes relevant to this guide

Reviewed against the official Full Version notes below. Earlier developer demonstrations retain their original source dates; this review does not verify unpublished costs or every release-build interaction.

1. Patch Notes #8A Documents Box transfer can fail independently of placing a case on a board; the latter receives another correction in #10.
2. Patch Notes #10Retest the exact Documents Box objective. A returned car missing from the board is not the same as a car still blocked out in the world.
3. Patch Notes #14The developer offers a cleanup action for duplicate equipment. Later #18 and #19 correct separate duplication triggers; do not collapse them into one universal resolved bug.
4. Patch Notes #18Do not use this historical note to claim FSR remains disabled: #19 re-enabled it the next day. Keep the cabinet pickup fix distinct from case-board objectives.

Patch evidence

Updated 2026-09-25. Historical demonstrations retain their original dates; a patch label is not a numeric build ID.