Sanctions Desk gathers and checks the evidence for every sanctions-screening alert and recommends an outcome; a person with the right entitlement approves it. One alert, start to finish · The problem it works on
Sanctions Desk / Recorded runs
Recorded runs
A few alerts from the committed run exports, shown step by step: which agent did what, which Nemotron model served each model call (local Lightning or cloud Ultra), the signed receipt for each call and whether it verifies, the Zetaris reads, and why a proposed close was stopped. The pages are built from the committed files by npm run site:build; the build stops if a receipt is missing or does not verify.
Customers and payments are synthetic; listed parties are public sanctions-list entries. Customer notes, payment references and list remarks are not shown, apart from the characters of a span the screener flagged and one phrase labelled synthetic on ALR-L0001, and identifier numbers are masked.
Outcomes: CLOSE_FALSE_POSITIVE = close as a false positive · ESCALATE_L2 = escalate to level 2 · NEED_MORE_INFO = ask for more information · RECOMMEND_BLOCK = recommend a block (two people must confirm). Raise-only: the policy guard can make an outcome more cautious, never less.
| Alert | Case | Desk recommendation | Label | Compared | Calls with a verified receipt | Run |
|---|---|---|---|---|---|---|
| ALR-0073 | Payment reference names a watched place | Escalate to level 2 (ESCALATE_L2) | Escalate to level 2 (ESCALATE_L2) | matches the label | 3 of 3 | routed-20261023T133311Z |
| ALR-0043 | Chain of 70 and 60 percent | Escalate to level 2 (ESCALATE_L2) | Escalate to level 2 (ESCALATE_L2) | matches the label | 7 of 7 | routed-20261023T133311Z |
| ALR-0030 | No date of birth on file | Ask for more information (NEED_MORE_INFO) | Ask for more information (NEED_MORE_INFO) | matches the label | 5 of 5 | sys2b-routed-20261023T195504Z |
| ALR-0058 | Cleared before; the listed entry's date of birth changed in the latest list | Recommend a block (two people must confirm) (RECOMMEND_BLOCK) | Escalate to level 2 (ESCALATE_L2) | acceptable | 3 of 3 | sys2b-routed-20261023T195504Z |
| ALR-0004 | Spelling variant of the name, different person | Close as a false positive (CLOSE_FALSE_POSITIVE) | Close as a false positive (CLOSE_FALSE_POSITIVE) | matches the label | 4 of 4 | sys2b-routed-20261023T195504Z |
| ALR-L0001 | A similar name with a conflicting birth date and another nationality; the note says the account is run for her uncle, Valeriy Igorevich Limarenko(synthetic), the listed person | Escalate to level 2 (ESCALATE_L2) | Escalate to level 2 (ESCALATE_L2) | matches the label | 4 of 4 | heldout4-sys4-routed-20261024T024523Z |
- ALR-0073: A payment whose reference names a watched place: the decision step proposed a close, the critic approved it, and the raise-only policy guard stopped it.
- ALR-0043: An ownership chain: the decision step proposed a close three times, the critic sent it back each time, and the guard escalated it because the critic's objection was still open.
- ALR-0030: A data-quality rule blocks a close: the customer has no date of birth on record, so the Zetaris rule dob_present_for_individuals fails, the policy guard blocks any close, and the case goes to a person as need more information.
- ALR-0058: An earlier clearance that no longer holds: the listed entry changed after the earlier decision, so the memory step marked it stale and the case was reviewed again.
- ALR-0004: A close: a spelling variant of a listed name with a different date of birth and nationality; the critic approved it, the challenger found no credible argument against it, and the guard let it stand for a person to confirm.
- ALR-L0001: A held-out case (labels written before the run): the structured fields alone would close it, but the local screener found a relationship to the listed person in the customer note, and the case was escalated.