Alert to SAR
Monitoring and screening produce alert queues. Cadre maps the work from triage through investigation and SAR-package preparation, with Conductor assigning specialists and the BSA officer retaining the filing decision.
Orchestration
Plans a supplied flagged case across triage, investigation, and package preparation, choosing the next step from each specialist result and retaining the path for review.
- hands the case to Alert triage
- hands the case to Case investigation
- hands the case to SAR package preparation
Detect
Transaction-monitoring scenario outputs enter the alert queue for triage.
Name-screening hits enter sanctions disposition with the supplied OFAC SDN evidence.
Triage & disposition
Front-line disposition of a monitoring-alert queue — close with a note, or escalate with reason codes.
efficientQueue triage is volume work; the frontier stays reserved for what escalates.
Clears, blocks, or escalates sanctions name-match hits from the supplied SDN evidence.
Pull refreshed customer due diligence into the case file when triage escalates. Open work. No Cadre blueprint is assigned to this step yet.
Inter-institution information requests on escalated cases. Open work. No Cadre blueprint is assigned to this step yet.
Investigate
Builds the investigation packet on escalated cases and recommends SAR / no-SAR, handing the sanctions screen to Cerberus as a focused specialist.
frontierCross-source investigation is the deep-reasoning seat in this process.
- hands the case to Sanctions disposition
File & review
Drafts the SAR from the packet, validates completeness, and routes the package for accountable approval.
sovereignSAR packages are confidential by statute; drafting never leaves the boundary.
Drafts from the investigation packet, checks the result against a completeness rubric, and revises without adding unsupported facts.
Escalated cases and filing decisions land here — the accountable approval point illustrated by Aarvion policy.
The external submission rail used after accountable approval; no Cadre blueprint owns this step.
Tune
Proposes detection-threshold changes and records whether the deterministic backtest clears its gate.
The walkthrough
- 1
Monitoring and screening outputs enter separate queues; Cadre begins with the cases supplied to its blueprints.
- 2
Sift works the supplied transaction-monitoring queue — close with a note, or escalate with reason codes.
Open example capture - 3
Cerberus compares a sanctions name-hit with the supplied SDN evidence, then clears, blocks, or escalates within its defined scope.
Open example capture - 4
Escalations open a case. Bloodhound builds the investigation packet and hands the subject to Cerberus for a fresh sanctions screen.
Open example capture - 5
On a flagged case the blueprints work as one: Conductor plans the case, routes each stage to the right specialist, and replans from every result.
- 6
In this example, Aarvion blocks submission without BSA-officer approval and sends the case back for review.
Open example capture - 7
Calibrate proposes a threshold change and records the backtest result; production adoption remains an accountable change decision.