Assess a simulated company under attack

01 · Role in the system

What Jev does here

For each investigated identity the lab sends a bounded evidence window and asks Jev four questions: a Noul compromise probability, a Choice classification with its distribution, a weighted 0-3 severity Score, and a Choice advisory response. Scenario ground truth stays separate from the model's input, and code owns telemetry generation, windowing, decision policies, and the investigation workspace. A packaged demo replays recorded jev-1.13.0 responses offline, and saved checkpoints expose exact inputs, distributions, and timing.

02 · Control boundary

Where Jev sits

Sliding telemetry windows to parallel typed judgments; deterministic policy turns judgments into an advisory investigation trail with replayable checkpoints.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

• Telemetry is synthetic and the lab never touches real infrastructure, so every judgment is advisory only.
• The published acceptance records cover fixed fixtures and browser performance, not detection accuracy against a labeled benchmark.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

• the-data-sherpa ↗Community · github · public · checked 2026-09-18