Jev Guard (Exchange Triage)

They are the author's own. The 100 samples are synthetic transfer events with author-assigned labels (72 pattern, 18 boundary, 10 injection), and the README says this measures pattern-recognition consistency, not a real-world laundering detection rate. On that set rules-only scored 68% and the Jev gate 50%. The eval runner refuses mock mode without --allow-mock, and no third-party benchmark is cited that cannot be traced.

Because the model never gets the last word. Blacklist, sanctioned-counterparty, and over-$500k rules run before any model call, and the action is composed in Java from direction and risk ordinal. Jev over-escalated 65 of 100 to manual review but missed zero freezes. Its own route answer is stored observation-only and agreed with the composed action 72% of the time.

Not on this evidence. Confidence is not saturated (62% of samples sat in 0.5-0.7) yet the highest-confidence bucket was the least accurate at 25%, and the sweep was flat at 50% accuracy for every pFreeze from 0.60 to 0.90. Gate on risk ordinal plus freeze probability, and use confidence only as a low-confidence fallback. Note also that noul answers arrive without confidence, so it is derived client-side.

Timeouts, 5xx, and 429 all degrade to MANUAL_REVIEW, never to an automatic pass, on the argument that annoying an analyst beats letting a transfer through. The blacklist is the catch: the mechanism is implemented but the data source is not connected, so it ships built-in sample data instead of a real sanctions list. The 24-hour feature window is in-memory, so a restart loses it.

It needs JDK 17+ and Maven. Run mvn spring-boot:run and then ./demo.sh to route five simulated deposit and withdraw events through the mock pipeline offline.

Measured on the real API with jev-1.13.0, about 395 input tokens and 36 output tokens per screening over a roughly 20-line state, or 75,268 input tokens for 100 screenings, at p50 about 272 ms.

No. The profile is in-memory, so restarting loses the 24-hour feature window; a Redis profile is reserved as an interface but is not yet load-tested.