Write it the way you would say it
Open the Rule studio and describe the behaviour you want to catch. Avus reads the action, the customer, the counterparty and the threshold in your sentence, and asks when a part could mean two things.
TipKeep one idea per rule. Two behaviours in one sentence make the backtest hard to read.
Raise a critical alert when a high-risk customer sends value to a counterparty with no EEA authorisation and more than 20% indirect darknet exposure within four hops.
Check what will actually run
Before anything else, look at the parameters the sentence compiles to, side by side with the version in production. This is exactly what the engine will evaluate, and nothing more.
Backtest it on your own history
Run the change over the last 180 days of your transfers. You see how many filed cases it would have caught, how precise it is, and how much extra work it would create for the team.
TipMissed filings matter more than alert volume. Look at that number first.
Stage it for a second approver
Staging sends the change to the approver your policy names. The person who wrote a rule can never promote it, and both names go on the record.
Promote v4 to productionStaged by the team lead
AwaitingWatch it after it goes live
Every version stays in the history with who changed what and why. The rule library shows how often each rule fires and how precise it is, so tuning becomes routine and rolling back takes one step.
More guides.
From alert to report
Follow one alert through evidence, a case and the escalation chain to a filed report.
Supervise the whole programme
Keep queues, quality, approvals and deadlines in view from one dashboard.
Prepare for an inspection
Give an examiner read-only access and export the record, without rebuilding anything.
See it on your own cases.
We will walk through this with your team, on a scenario you choose.