Write a rule
the way you'd say it.
Describe a monitoring rule in plain English. Backtest it against last quarter. Approve it when it is ready: deterministic, versioned, and audit-ready.
05Monitor in action
Plain English compiles to trigger, condition, and action.
>3 wires under $10k · rolling 7 days · high-risk jurisdiction
RUL-0007
This rule fires when an investor makes a 4th qualifying wire within any 7-day window.
Wire activity
Rolling 7-day window
- 1Wire · $6,100Clear
- 2Wire · $7,250Clear
- 3Wire · $9,300Clear
- 4Wire · $8,4004th in 7 daysFlagged
CASE-2026-0412 · RUL-0007 v1
Context auto-attached: investor profile · 7-day wire history · rule version
Plain English becomes enforceable logic.
Trigger, condition, and action. Compiled from the words your team already uses.
Ops drafts the rule. Compliance approves the version that goes live. The system never invents a judgment; it only fires what a human signed.
Backtest before you believe.
Every draft runs against history. Shadow mode before anyone arms it.
See how many wires would have flagged last quarter, review the false positives, then promote only the version your compliance officer trusts.
Alerts that end in answers.
Cases arrive with context attached. Narratives draft themselves. Humans close the loop.
Investor profile, recent wires, and the rule version travel with every case. Disposition is named, reasoned, and exportable for a regulator without leaving the register.
Rules, cases, and register rows share one audit trail, from fund registration to last wire. See fund setup →
Fund operations don't need another tool.They need one system that replaces ten.