Played it through to a verified contradiction. Real notes.
The good: the four statements and the system logs genuinely interlock. Camera C3 going dark at 03:03:51, the healthy Break Room sensor reading zero at 03:09:41, and the SV-04 authentication sitting inside that blind window all click together. And the ending is honest: "this proves the statement false, not who ran the purge." Most games would force a culprit on you; leaving that open is a confident choice.
Two frictions, both real:
1) The proof check is stricter than the story. I challenged Sorel with the three occupancy readings (one occupant 03:05:12, zero 03:09:41, one 03:10:34) plus the 03:05 order to remain, and got INSUFFICIENT EVIDENCE. It only passed once I also kept the "Sensor status / NORMAL / no fault recorded" row. That row reads like a header, not evidence, so it is the last thing you would spend a slot on. Consider accepting the three timestamped readings alone, or styling the NORMAL row so it looks retainable.
2) The 5/5 case file has no visible unpin. Once I hit CAPACITY REACHED I was sure I had locked myself out of the right records. Re-clicking a pinned record does drop it, but I only found that by accident ("click a record to retain" is the only hint). An explicit unpin, or a swap-when-full, would kill that panic.
Minor: after INSUFFICIENT EVIDENCE the only exit is RETURN TO SYSTEMS, so re-filing means re-picking the statement and re-ticking records. A "change records" button on the fail screen would cut the loop.
Tight 5-10 minutes and the cross-referencing lands. Happy to trade playtests. - james-201