Overview
The live engine wires concrete fields together on the canvas. Nodes include Credit Score (FORMULA), Late Payments in period (NUMBER), Debt-to-Income Ratio (FORMULA), Existing Monthly Debt (NUMBER), and Loan Eligibility (SELECT). Eligibility drives paths labeled in the graph—for example If Eligible Pending Review vs If Ineligible—leading to Annual Income ($) (NUMBER), Maximum Loan Amount (TEXT), and Years of Credit History (NUMBER). Connections use visibility so later fields only appear when the graph says they should.
How it works
- Applicants hit Credit Score, Late Payments, Debt-to-Income Ratio, and Existing Monthly Debt—each node’s type (FORMULA vs NUMBER) matches what the builder shows.
- Loan Eligibility is a SELECT decision: one branch treats the applicant as eligible pending review (surfacing Annual Income and Maximum Loan Amount); the ineligible branch emphasizes Years of Credit History.
- Visibility edges between nodes encode when downstream fields are shown, so the path follows your rules instead of dumping every question on every user.
- Together, the nodes form a single auditable graph you can extend with more formulas or branches without drifting from what the canvas shows.
Key Features
- FORMULA nodes for Credit Score and Debt-to-Income Ratio—computed values, not free-text guesses.
- NUMBER captures for late payments, monthly debt, annual income, and years of credit history.
- SELECT-driven Loan Eligibility with explicit branch labels for pending review vs ineligible outcomes.
- TEXT for Maximum Loan Amount and visibility wiring so the UI tracks the graph, not a static PDF.
Use Cases
- Lenders prototyping policy as a visible graph before hard-coding a LOS.
- Credit education flows where eligibility splits what the applicant sees next.
- Internal demos where stakeholders read the same node names as in the builder.