Silent changes
Tuning that nobody signed
Engineering raises a threshold to fix a queue backlog. The change works, the backlog drops, and nobody in compliance approved a lower level of coverage.
Risk and Governance squad
Dasha Relia — Lead AI Compliance-Reliability Engineer
AI compliance engineer for rule and model changes
Dasha Relia — Lead AI Compliance-Reliability EngineerDasha Relia is an AI agent that adds compliance gates to your change process. New rules, models and configuration changes are checked against your controls and signed off by a named person before go-live. After release she watches for compliance drift and flags it to the owner with the change that likely caused it.
Dasha Relia
Change request: new velocity rule
IllustrativeReady for sign-off
Gate checks · 2 open
Flag explained
“Rule lowers alerts on one scenario. No test evidence attached.”
Job description
What Dasha Relia does Job description
Dasha Relia is a Lead AI Compliance-Reliability Engineer. She sits in your change process for compliance systems and checks that every rule, model and configuration change carries an owner, test evidence and a sign-off before it goes live.
AI AGENT · RISK AND GOVERNANCE SQUAD
DASHA RELIA
Lead AI Compliance-Reliability Engineer
REPORTS TO
Your Head of Compliance or model risk lead
WORKS WITH
Your change tickets, rule and model repositories, release pipeline and monitoring systems
DEPLOYED
Shadow mode first, then the autonomy you set
KEY RESPONSIBILITIES
01Add compliance gates to your change process for rules, models, thresholds and agent settings
02Check each change for an owner, test evidence, expected impact on alerts and a named approver
03Hold a change at the gate for review if you set her to, until the named approver signs
04Watch released changes for compliance drift and flag it to the owner with the likely cause
05Keep a change record your examiner can follow from request to release
AUTONOMY MODEL
LOWMEDIUMHIGH
Low risk
Can mark a routine change's checks complete, if you allow it
Medium risk
Goes to the change owner and compliance by default
High risk
Always goes to your compliance lead for sign-off
You set the threshold per rule.
Kill switch: Turn Dasha off at any time
Options
How the options compare
| CRITERIA | Manual change board | Pipeline checks only | Dasha Relia |
|---|---|---|---|
| Compliance review of changes | If someone raises it | Code quality, not compliance impact | Every change you mark as compliance-relevant |
| Who signs off | The change board | Engineering | A named compliance approver |
| Evidence kept | Minutes and tickets | Build logs | Owner, tests, impact, approver, in one record |
| After release | Nothing until the next review | Uptime and errors | Watches for compliance drift |
| Pace of release | Waits for the next meeting | Fast | Adds a gate step, routine changes move quickly where you allow it |
| Where it's weaker | Slow, and misses changes nobody brings | Blind to compliance impact | Only sees changes that go through connected tools. Hotfixes made outside them stay invisible to her |
Works best with
AI agents that work best with Dasha Relia
Dasha guards the gate. These agents supply the checks and controls she gates against.
RISK AND GOVERNANCE
Devon Pulse
Lead AI DevSecOps Pipeline Architect
Adds security scan results to each change before Dasha's compliance gate.
Meet DevonRISK AND GOVERNANCE
Zara Trustwell
Director AI Regulatory Compliance
Supplies the approved controls each change is checked against.
Meet ZaraRISK AND GOVERNANCE
Riya Intel
Director AI Governance & Model Risk
Provides model validation and version records for model changes at the gate.
Meet Riya
Thoughts that matter
Insights on AI agents, financial crime and compliance
What we're learning about AML, fraud and the evidence examiners ask for.
Best AML Software in 2026: An Honest Comparison for Banks and Fintechs
Read More
goAML Registration and STR Filing in the UAE: A Step-by-Step Guide for Reporting Entities
Read More
Transaction Monitoring Software: UAE Acceptance Checklist
Read More
PEP and Sanctions Screening: What the MLRO Owns
Read More
Session Risk Scoring: Continuous Authentication for Banks
Read More
Impossible Travel Detection in Banking: How It Works
Read More
Questions? We Have Answers
-1.svg)
Frequently Asked Questions
Still have questions?
Talk to the people who build the agents. We'll answer per capability, yes or no.
An AI compliance engineer checks changes to compliance systems before and after release. Dasha Relia looks at each rule, model or configuration change for an owner, test evidence, expected impact and a named approver, then watches the change in production for compliance drift.
No. A named person signs off every change that touches thresholds, models or coverage. Dasha can mark a routine change's checks complete only where you allow it, and can hold a change at the gate for review if you set her to. A kill switch turns her off without touching your release process.
It's when a rule, model or setting starts catching something different from what it was approved to catch. Customer behaviour shifts, data feeds change or a later change interacts with an earlier one. Dasha compares live results with the expected impact recorded at release and flags the gap.
Dasha reads your recent change history and live results, and reports what she would have flagged or held. Nothing in your release process changes. You compare her findings with your last change audit and decide what to switch on.
Access to change tickets, rule and model repositories, screening and monitoring configuration, and alert volumes over time. Past audit findings on change control help her focus on what your examiners have already raised.
No. Your tickets and pipeline stay as they are. Dasha adds a compliance gate and a change record on top.
FluxForce runs as SaaS, on-premise or hybrid, built on Microsoft Azure. We agree data residency and which components run inside your environment during deployment design, before any data moves.