01Journeys are configuration, not code
One lender wants DigiLocker, another insists on CKYC, a third accepts a document upload. One wants video KYC before sanction, another after. In most platforms each of those is a release.
In MODNAR a journey is a versioned document attached to a lender's product, drawn as a flow: drag a step past the sanction diamond to run it later, insert one on an arrow, publish. The next application runs the new flow, and applications already in progress keep the version they started on. The borrower journey and the LOS stage tracker render from the same definition.
02AI in the underwriting seat
Not a chatbot in the corner. The credit memo is assembled from the bureau report, the bank statement analysis and the KYC record: the same evidence a credit officer would read, in the document they would have spent forty minutes writing.
The recommendation comes with the factors it weighed and the ones that gave it pause, so an underwriter can disagree with the reasoning rather than argue with a score. Underwriting can run manually, on rules, or assisted by a model you choose. In the prototype the memo is drawn from demo data.
03Multi-tenant from the first line
Not a single-lender product to be made multi-tenant later. Every record carries its tenant, and each lender gets its own branded journey, its own products, its own credit policy and its own users, operated from one platform.
The design isolates lenders with row-level security on the tenant in the database, rather than by developer discipline. Today's browser prototype shows this on the tenant screen; enforcement on the server arrives with the server-side core.
04The rules engine is yours
The decision policy is the secret sauce of any lender, and it should never sit inside a vendor's release cycle. In MODNAR the BRE is configuration: go and no-go boundary conditions, refer rules, segments that shape the offer, and the models behind them.
Rules today, a scorecard as challenger on a slice of traffic, a PD model scoring in shadow until it earns the seat. A simulator shows what any change does before it is published, every version can be rolled back, and each decision records the version it ran on.
05Every integration is visible
Bureau, PAN, DigiLocker, account aggregator, penny-drop, e-sign, mandate and payout. Each call is logged against the application that triggered it, with the request, the response, the status and the latency.
Open any application and the whole vendor conversation is there in order, including the retries and the calls that failed. The same log answers the operations question and the finance question: what happened, and what it cost. In the prototype these calls go to sandbox stubs.