Rules engine - policy in plain language
Route: /rules-engine
Purpose
The rules engine encodes bank policy as explicit if / then logic (thresholds, prohibited segments, required documents)-different from statistical models that estimate risk scores.
What you see (typical)
- Catalog of rules with version or effective date (depends on implementation).
- Test / simulation area (if enabled) to see which rules fire for a sample case-use only with synthetic or masked data per bank policy.
What happens when a rule changes
- New decisions evaluate the current published set after activation.
- Audit should show who published and when-compliance uses this alongside model change logs.
Rules vs models (for committees)
| Rules | Models |
|---|---|
| Deterministic policy | Statistical estimation |
| Explainable as “because policy says…” | Explainable as “because similar past cases…” |
| Often faster to adjust with governance | Needs validation cycle |