The vocabulary
The actions of lending, with the rules built in.
Every action a co-worker takes is one of 500+ validated, credit-native primitives, the atomic operations of regulated lending. The list is finite; what you build from it isn’t.
What a primitive is
The smallest action that already knows the rules.
A primitive does one thing, like making a call, generating a notice or moving a payment, and carries its own safety inside it. Because the building blocks are validated, everything built from them inherits that safety.
Validated before it runs
Each primitive ships with its own checks. The action clears its rules first, or it never fires, and the exception is logged with the reason.
Metered as it works
Every primitive self-meters in Krim Work Units. The cost of an action is explained line by line, not asserted: the same record that bills it.
Logged by construction
Explicit inputs and outputs, written to the audit trail and versioned the moment it completes. Nothing to reconcile, no loose ends to chase later.
The library
Bureau pulls, payments, notices, calls. The real work, ready to run.
The 500+ primitives span 20+ domains of the work a lender actually performs, from voice and documents to compliance, data, payments and decisions, so there are no generic tool-calls for an integrator to assemble. It ships credit-native.
Voice & telephony
~45Placing, transferring and capturing live conversations.
Document operations
~30Generating, reading and signing the paper of regulated work.
Compliance checks
~50The rule-tests an action must pass before it is allowed to run.
Data operations
~35Fetching, updating and enriching the records work runs on.
Payment processing
~25Calculating, verifying and moving money under the rules.
Decision logic
~20Evaluating policy, resolving conflicts and routing to people.
Analytics & reporting
~15Rolling up metrics and producing the reports auditors expect.
Integration
~30Reaching the systems you already run, in both directions.
Testing & QA
~10Exercising co-workers safely before they ever touch production.
Custom
—Tenant-specific primitives, built to the same construction.
A representative ten of the twenty-plus domains · counts approximate
How they compose
Every co-worker is assembled, never hand-coded.
Co-workers are composed from these primitives the way sentences are composed from words. Take MAKE_CALL, the validated action that places an outbound call: the same primitive underlies a collections call, a retention call and an onboarding call. Only the policy, script and segment change, and the compliance checks come built into the primitive.
Change a rule once.
It lands everywhere.
Every co-worker in KrimOS speaks this one vocabulary, so a check written once protects every workflow that ever uses it.
The layer that gets you past Compliance and Legal.
Build on a vocabulary that is validated, metered and logged at the root, and every co-worker you compose is accountable from its first action. Next, the co-workers that put the vocabulary to work.
See Kriya at work.
Run the whole operation on KrimOS, or layer it onto the systems you have.