AML alert triage
Onboard and screen a customer with the aml example, park at the BSA officer gate, sign it, and keep the run monitoring — every SAR and OFAC action stays shadowed until a human signs.
Scenario. A new customer is onboarded and screened against sanctions and adverse media. Clear, low-risk parties auto-onboard; a high-risk party is escalated, and a BSA/AML Officer must sign the high-risk onboarding, any OFAC action, and every SAR before it is filed.
Example: aml · Parks at gate step-id: bsa-gate (gate:bsa-officer-signoff).
1. Import the example
curl -s -o aml.process.json https://minctrl.com/examples/aml.process.json
jq -n --slurpfile doc aml.process.json '{document: $doc[0]}' \
| curl -s -X POST "$API/process-templates/import" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
--data-binary @- | jq '{slug, version, executable_violations}'The example is now a process in your company under the slug aml
(see Example processes for registering first).
2. Start the run
RUN=$(curl -s -X POST "$API/process-runs" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"vertical": "aml",
"draft": true,
"inputs": {
"customer_name": "Jane Q. Public",
"customer_country": "US",
"customer_dob": "1980-04-12",
"risk": "high"
}
}')
RUN_ID=$(echo "$RUN" | jq -r .id)The run screens concurrently, scores onboarding risk, and — for a high-risk party —
parks at the BSA officer gate. risk is the routing input the resolver matches
against the branch labels: "high" routes to enhanced due diligence and the gate;
a clear, low-risk party auto-onboards and never parks.
3. Read where it parked
curl -s "$API/process-runs/$RUN_ID" -H "Authorization: Bearer $TOKEN"status is awaiting_human. The trace shows the run parked at the bsa-gate step. Use
that step-id to resume.
4. Resume — the BSA officer signs
curl -s -X POST "$API/process-runs/$RUN_ID/resume" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"gate": "bsa-gate",
"decision": "onboarding approved"
}'decision records the officer's verdict. The bsa-gate routes on that verdict — for
example onboarding approved, SAR signed, or sanctions hit confirmed: block/reject + OFAC report. A denial or reject verdict leaves downstream irreversible actions unauthorized.
5. Outcome — the run keeps monitoring
Unlike a one-shot approval, AML monitors continuously. After the signed onboarding
decision is applied, the run maintains a monitoring loop, triaging transaction alerts;
a true hit drafts a new SAR and parks again at the BSA gate. Expect this run to loop
rather than terminate — the engine bounds the loop with a step budget, so the API
reports status: "max_steps" once the budget is exhausted.
Governance note
The irreversible steps here — execute the OFAC action, apply the onboarding decision,
and file the SAR with FinCEN — are reversible: false and stay shadowed (dry-run)
until you opt a connector in. They only fire for real after the BSA officer's signed
verdict authorizes them, and only if you have un-shadowed the connector deliberately.
Example processes
Six of the example processes from minctrl.com/flows, imported into your company and run end to end — import, start a run, it parks at a human gate, sign, outcome.
Prior authorization
Turn a prior-auth request into an approval or a clean determination with the prior-auth example — a medical director signs every denial before it transmits.