Skip to content

02 · Engine

Engine.

One engine runs every lending workflow in a fixed order. AI works only inside the steps that need it, a second model checks its work, and a person signs.

On the LOS or LMS you already run · or on ours

Workflows

AI only where it helps.

Every workflow is fixed steps with their branches, drawn and versioned. Most steps are plain code or your Rules. Agents read documents and draft requests inside a step, in parallel where they can, and never choose what happens next. Here, a consumer Pack collects a complete file, asking the borrower again until nothing is missing.

  • Any lending workflow, in a fixed order
  • AI only inside a step, never choosing the next one
  • Tailored to each lender with Rules, not code
  1. Open the file (code)
  2. Build the checklist (Rules)
  3. Anything missing? If yes: an Agent drafts the request, a person approves it, the borrower uploads documents, and the checklist runs again on what came in.
  4. If nothing is missing: Agents read the pay stub, the bank statement and the photo ID in parallel
  5. Merge the facts (code)
  6. The AI Reviewer reviews every claim
  7. A person clears each item at the HITL Gate
  8. Write to the loan system and the Audit log (code)

Agents and the AI Reviewer

One model does the work. A different one checks it.

An Agent reads the file and cites the page. The AI Reviewer is a second model that sees the claim and the cited page, never the Agent's reasoning, and says whether the page supports it.

The HITL Gate

A person signs. Declines are never automatic.

Every step that changes a borrower's file stops at a HITL Gate. Your Approver sees the claim, the evidence and the review, then approves, edits or sends it back, with a note on the record.

FAQs

Questions about the Engine

All questions
What are the AI agents?

Agents are the AI that works inside a workflow's steps. They read documents, cite the page each fact comes from, and draft requests, in parallel where they can. The workflow and its Pack decide which Agents run, and where. Agents never choose the next step, and they can't write to your systems.

What does the AI Reviewer do?

The AI Reviewer is a second model that checks the Agent's work. It sees the claim and the cited page, never the Agent's reasoning, and says whether the page supports the claim. Anything it can't confirm goes to a person.

One claim, checked
  1. Agent cites the page
  2. AI Reviewer reads the same page
  3. Supported, or to a person
What is a HITL Gate?

A HITL (human in the loop) Gate is the step where a person signs. Every step that changes a borrower's file stops there. Your Approver sees the claim, the evidence, and the review, then approves, edits, or sends it back with a note on the record. Nothing is written until they sign.

At the HITL Gate, the Approver
  1. Approves
  2. Edits, then approves
  3. Sends back, with a note
Can the Agentic Engine decline a loan?

No. Declines are never automatic. Agents prepare and recommend, and your people decide. Every recommendation reaches a person at a HITL Gate with its evidence, and the person who signs is on the record.

Can we create our own agents?

Yes, inside your workflows. Agents always work inside a workflow's steps, so new agent work is added as a step in a workflow or a Pack. We build workflows and Packs with you, and you tailor them with your own Rules, without writing code. Need a product we haven't built? We'll build its Pack with you.

Pick one workflow. Run it on your files.

We'll set the Engine up on one of your workflows, read-only first, with your people at every HITL Gate.