METHODOLOGY / SCOPE
Know what
the evidence means.
This note describes the documented Sentinel 0.5.0 analysis methodology. Assessment scope, parser compatibility and feed availability are established for each operation.
Detector roles are deliberately separate.
The reviewed registry contains four verdict-bearing detectors, two coordination screens, one account/infrastructure corroborator and two experimental telemetry detectors. Only verdict-bearing detectors set the case tier. Screens, corroboration and experimental observations cannot do so alone.
Synthetic validation has a specific boundary.
The documented tests use synthetic statistical-row controls. Exact 95% Clopper–Pearson confidence intervals are checked against an upper false-positive bound of 5% and a lower power bound of 80%. Those are test gates, not a statement about live detection performance.
The source report describes 22 arms: five game-sensitive detectors across four game regimes, plus two game-independent detectors. Parser support covers NLH, PLO4, PLO5 and PLO6. Functional PLO parsing tests do not establish calibrated detection on real operator hands.
Field calibration is a separate step.
Real-hand performance requires operator-labeled calibration. The assessment should consider the room, sample, player population, game and evidence feeds. No universal accuracy percentage is claimed here.
Missing feeds remain coverage gaps.
Gameplay and seating/session evidence can be available from hand histories. Timing may be partial. Rich action, connection, hashed device and network records require additional feeds. Experimental automation and disconnect observations remain observation-only.
Reproducibility starts with identity.
Hand identity is composed of room, corpus snapshot and hand ID. Analyses are isolated by game and a run manifest is persisted. The website’s case examples contain fictional identifiers, use illustrative values and do not connect to a live investigation.
Agree the operating scope.
Before sharing player data, agree the applicable release, adapter coverage, access controls, retention and secure intake. For an initial discussion, email support@sentinelpokersecurity.com. Do not send raw player data or credentials in the initial inquiry.