Rules outside the code, with versions.
Your credit policy is a DMN decision table — the OMG's open standard. Anyone who reads the table understands the rule without knowing how to code, and auditors don't need a translation.
| # | score | debt-to-income | monthly income | outcome | limit |
|---|---|---|---|---|---|
| 01 | < 500 | — | — | DECLINE | — |
| 02 | 500 – 699 | ≥ 40% | — | DECLINE | — |
| 03 | 500 – 699 | < 40% | ≥ 3,000 | REVIEW | — |
| 04 | ≥ 700 | < 40% | ≥ 3,000 | APPROVE | up to 8× income |
| 05 | ≥ 700 | < 40% | < 3,000 | REVIEW | — |
| 06 | ≥ 780 | < 25% | ≥ 8,000 | APPROVE | up to 12× income |
No deploy, no queue
The risk team publishes a new version. The service that calls it doesn't change, doesn't restart and doesn't even notice.
In a single call
The decision comes back in the response to the same call. With the pipeline, fetch time and rule time are broken out.
The XML is yours
The whole policy can be exported through the API, in an open standard. No proprietary format locks your operation in.
What a decision table is
DMN (Decision Model and Notation) is the OMG standard for writing business rules as tables. It's the format the engine runs and the one the console's editor draws.
- Inputs
- The columns on the left: the fields the rule reads — score, income, debt-to-income, amount requested. They come from your system or from the pipeline.
- Rules
- Each row is a rule. Cells use FEEL expressions, the standard's language:
< 500,[500..699],>= 0.4.
- Hit policy
- Today the engine applies the first rule that matches (the FIRST hit policy), top to bottom. Row order is part of the policy.
- Outputs
- The columns on the right: the outcome and what comes with it — limit, a readable reason for a decline or a review.
- Version
- Every change becomes a new version, which only takes effect when someone publishes it. A draft decides nothing.
Draft, published, archived
The engine validates the DMN before saving a version. Publishing puts it live; archiving the version that went wrong brings back the previous published one — no deploy in any of the three.
In the console's visual editor, or by importing the XML you already have.
Run a case against the new version before publishing and read the trace.
The next call already uses the new version. The previous one stays in the history.
Archive the new version and the previous published one takes effect again.