KhojAI Niyam · the rule engine

Every record checked against every rule.

Write the rules as plain sentences. Niyam checks every record overnight and hands the reviewer a finished file.

See how a rule is written

Niyam · review queueCredit file 4,1821 failed · 1 undeterminedPrepared 04:12 — overnight batch

Record: Credit file 4,182
Type: Secured term facility
Rules applied: 6 of 6
Ruleset: rev 41 — 12 Bhadra

Pass
Borrower identity documents present and unexpired
PARTY, PARTY_DOC — 3 rows · latest expiry 2029-04-11
Pass
Exposure within the single obligor limit
EXPOSURE, CAP_BASE — 2 rows · 11.4% of core capital, limit 20%
Fail
Security valuation dated within the last 12 months
COLL_MASTER, VALN — 1 row · valued 2024-11-02, 418 days
Pass
Approval authority matches the exposure band
APPROVAL, AUTH_MATRIX — 2 rows · band C, approved by Credit Committee
Unknown
Beneficial-ownership declaration on file
BENEF_OWNER — 0 rows returned · source unreachable, not read as absent
Pass
Insurance assignment recorded against the security
INS_POLICY — 1 row · assignment noted, expiry 2026-09-21
Renew the assignment before 21 Sep

Niyam never closes a record
Read-only against the system of record
Every run stored, never overwritten

Every verdict shows the rows it was reached from. Rule 6 passed and still needs someone to act.

Writing a rule

Write a rule the way you would say it.

Write it in ordinary words. Niyam works out which data it means and runs it from the next batch.

Written by compliance

In plain language

Rule name: Security valuation currency
The rule: If the facility is secured by property, the valuation must be dated within the last 12 months.
It concerns: collateral · valuations · facility type

Resolved by Niyam

Against what your data means

facility type: FAC.SEC_TYPE
collateral: COLL_MASTER
valuation date: VALN.VAL_DT
join path: FAC → COLL_MASTER → VALN

Read from your system's business layer, not guessed from column names.

Runs from the next batch

On every record

Fail: File 4,182
VALN.VAL_DT: 2024-11-02
Age: 418 days — limit 365

Tied to ruleset rev 41. Next year it still reads against this wording.

No engineering release in between. A rule suggested today runs tonight.

Results and actions

Passing a rule and needing action are two different things.

A record can pass and still need action. One label loses one — usually the good news.

Verdict	No action needed	Action needed
Pass	Clean record — nothing to do	Compliant, and somebody must actBoth reported
Fail	A compliance problem to resolve	A problem, plus a separate actionBoth reported
Unknown	Couldn't determine — needs a look	Couldn't determine, action outstandingBoth reported

Result and action have their own badges and filters, so a passing record with an open task still shows up.

Evidence

A result you can still explain next year.

Four things travel with every result. All four matter a year later.

FailSecurity valuation currency

Rule, as it read that day

“If the facility is secured by property, the valuation must be dated within the last 12 months.”

ruleset rev 41 · frozen at evaluation

Data retrieved

FAC 4182 · SEC_TYPE = PROPERTY COLL_MASTER 9910 · VALN 22417 VALN.VAL_DT = 2024-11-02 (1 row)

Reasoning

The facility is property-secured, so the rule applies. The most recent valuation is 418 days old, which exceeds the 365-day limit.

Run

2026-08-30 04:12 · batch 7731 written as a new record — run 3 of 3 retained

Where KhojAI Niyam fits

Most tools do one half of this job.

You probably run some of these already. Each covers part of the work.

Chat over the database answers fluently and can show nothing. It demos best and proves least.

Where we stop: a ready-made product for your industry beats us on day one. A rules engine is cheaper for simple checks. A GRC platform still owns policy. Niyam covers the middle.

Common questions

Ten questions people ask about KhojAI Niyam.

What compliance teams ask first.

01Can our compliance team write a rule without an engineering release?

Yes. Rules are plain sentences, live from the next batch. Put an engineering release in the path and the rule library falls behind the backlog.

02How does Niyam know what our data means?

It reads your system's business layer, not just column names. Guessing at that produces answers that are confident and wrong.

03Can Niyam say “I don't know”?

Yes. "Undetermined" is a real result. When the data cannot be read, Niyam says so rather than calling it clean.

04Can a record pass and still need action — and does Niyam show both?

Yes. Result and action are separate, with their own badges and filters.

05Once somebody handles an action, what closes it — and what reopens it?

That depends on your process, so we walk through it with you. An action nothing closes becomes a list nobody reads.

06What happens when a query comes back empty or invalid?

It fails loudly. An empty result is never read as "nothing wrong".

07Can I see a result from three months ago, with its evidence and the rule behind it?

Yes. Every result is frozen against the rule text that produced it, and every run is kept.

08Where does our data go?

KhojAI runs on your infrastructure. Ask us about inference, embeddings, logging and monitoring separately — four different paths.

09What does one record cost?

We show you the sample size, the rule count, and whether the model's own reasoning is counted. That last part is often left out.

10Who is accountable for the final decision?

A person, always. Niyam prepares the file and never closes a record.

Bring us one rule and one record.

Bring a rule from your procedure document and a record it applies to. We will show you what Niyam returns, and what it refuses.

Back to the KhojAI platform

Licensed as an add-on to KhojAI. It can read systems KhojAI does not otherwise index.