Policy simulator

Move the limits. See which rule decides.

This is the same table that goes to production. Changing a number here is what the risk team would do on a Tuesday — without asking anyone for anything.

Score742
IncomeR$ 6,400
Debt-to-income31%
APPROVE

Score above 700 and debt-to-income below 40%.

rule 04 · sample policy

#ScoreIncomeDTIDecision
01< 500——DECLINE
02500–699> 4,000< 30%REVIEW
03500–699—≥ 30%DECLINE
04≥ 700> 2,500< 40%APPROVE
05≥ 700—≥ 40%REVIEW

A sample policy, with five rules and the first match winning. In the console, the same test runs against your real version and returns the trace.

Today, in the console

One case against the new version

Before publishing, run an input against the draft and read what came back: the rule that matched, the output and the path of the evaluation. It's the policy's dry run.

Input
The fields the table reads, filled in by hand or pasted from a real decision.
Output
Outcome, limit, queue — what the version would return in production.
Trace
Why it came out that way: the row that matched and the conditions evaluated.
Environment
Tests don't count toward your allowance and can't see production.