Glossary · Lokta concept vocabulary

Deterministic core

A deterministic core is the layer of a lending platform whose outputs are fully reproducible from inputs and policy: no probabilistic models, no LLM calls, no hidden randomness.

  1. Recorded inputs
  2. Rule version
  3. Reproducible result
Illustrative example

Two auditors, a year apart, ask why a particular account was classified NPA on a particular day. A deterministic core answers both the same way: here are the repayments as posted, here is the day-end days-past-due count, here is the classification rule in force, here is the result. If the answer could differ between the two visits, the lender has an explanation, not a record.

Interest calculations, repayment allocation, NPA classification, and the audit log all live here. A deterministic core gives the lender a system of record that auditors and regulators can interrogate. AI layers (workflow assistants, agents) sit above it and call into it; they never replace it. The architectural rule: the deterministic core is the truth, the AI layer is the help. Read as the sequence a single action runs through: AI proposes, the core decides, the record proves it. The essay AI in lending, the deterministic core makes the full argument.

On the live book the core is what turns an agent's suggestion into something a lender can stand behind. The agent may read a borrower conversation and propose a waiver, a date change or a settlement. The core recomputes the schedule, checks the proposal against the policy version in force and the approvals it requires, posts the result or rejects it, and writes the whole sequence to the audit log. Nothing probabilistic touches the ledger.

Does a deterministic core mean no machine learning anywhere?

No. It means machine learning does not decide what posts. Models can score, rank, draft and propose above the core; the core owns the arithmetic and the state. A model that predicts which accounts will roll into the next bucket is useful. A model that computes the interest on them is a liability, because its answer cannot be reproduced on demand.

How is a deterministic core different from a rules engine?

A rules engine evaluates conditions; a deterministic core is the system of record those conditions act on. The core holds the loan, the ledger, the schedule and the log, and guarantees that the same inputs and the same policy version produce the same outputs. A rules engine can sit inside it, and usually does. What the core adds is state, replay and proof, which a rules engine on its own does not have.

Why do regulators care whether the core is deterministic?

Because supervision runs on reconstruction. A model-risk reviewer, an internal auditor and a borrower’s ombudsman complaint all ask the same question in different forms: show how this number was produced. A deterministic core answers by replaying the inputs and the policy. A probabilistic one can only describe how it usually behaves, which does not satisfy a question about one account on one day.

Founder-led adoption

Adopt the agentic loan servicing platform.

Lokta is built for enterprise deployment, VPC or single-tenant cloud, with an audit trail in every state change. We work with a select group of institutions through a founder-led model: deep adoption, deliberate scope, a delivery window the team commits to in writing.