Jev Guard Risk Triage
Triage deposit and withdrawal events with Jev while deterministic rules retain final control.
Triage deposit and withdrawal events with Jev while deterministic rules retain final control.
After deterministic hard rules pass, the transfer-screening service renders sanitized transfer features as state and asks Jev for a five-level risk Score, behavioral-pattern Choice, freeze Noul, and suggested-route Choice. A separate gate combines the risk ordinal, confidence, freeze probability, transfer direction, and configured rules to select auto-pass, manual review, or freeze. The route Choice is logged for comparison and does not control routing.
Assess the transfer's overall money-laundering or fraud risk from the supplied features.
State is a sanitized line-oriented summary of transfer direction, chain, token, USD amount and band, address age, recent transfer count and volume, counterparty label, first interaction, burst, night-operation, and blacklist signals when available. This is a request shape, not a real transfer or observed answer.
Choose the behavioral pattern that best describes the transfer.
State is a sanitized line-oriented summary of transfer direction, chain, token, USD amount and band, address age, recent transfer count and volume, counterparty label, first interaction, burst, night-operation, and blacklist signals when available. This is a request shape, not a real transfer or observed answer.
Do the risk signals justify immediately freezing this transfer pending review?
State is a sanitized line-oriented summary of transfer direction, chain, token, USD amount and band, address age, recent transfer count and volume, counterparty label, first interaction, burst, night-operation, and blacklist signals when available. This is a request shape, not a real transfer or observed answer.
Choose a suggested route: automatic pass, human review, or immediate freeze. This answer is recorded for comparison and does not control routing.
State is a sanitized line-oriented summary of transfer direction, chain, token, USD amount and band, address age, recent transfer count and volume, counterparty label, first interaction, burst, night-operation, and blacklist signals when available. This is a request shape, not a real transfer or observed answer.
The service derives transfer features, then checks amount limits, blacklist, and sanctioned-counterparty rules; a hard-rule hit returns without calling Jev.
If no hard rule fires, the service sanitizes and renders the available transfer features and submits the four questions from risk-rules.yml.
The policy gate combines the answers with configured thresholds to choose auto-pass, manual review, or freeze. A Jev outage falls back to manual review, and the decision is logged.
This design places Jev behind deterministic vetoes and an explicit policy gate. It records a route recommendation without allowing that recommendation to override the audited routing logic, and degrades to manual review if the upstream call fails.