It can't make it up.
Every answer comes from the actual rule, with the citation shown. If the answer isn't in the rules it holds, it tells you so — it won't guess from memory.
On a device your bank owns.
Codices is a small device that gives your desk a private assistant for the rules you lend under. Ask it a question, it answers — and shows you exactly which rule it's reading from, and the date that rule is good through. It never touches the internet, because it never needs to.
Our borrower is a living trust. How does it take title, and what can we rely on?
Up to date as of July 1, 2026 · citation checked against the official text
Illustration · examples for demonstration
The problem
Codices runs on the same kind of AI as the frontier models — it's built from that lineage, and we're glad to say so. The difference isn't the intelligence. It's everything around it: where it lives, what it reads, who can reach it, and whether it ever leaves the room.
The frontier keeps its intelligence in the cloud — fed by the whole internet, rented by the question, and reachable by whoever holds the servers. Codices seals the same kind of intelligence in a device you own — fed only by the rules, answering only from the source, reachable by no one.
Cloud AI asks you to trust it. Codices is built so you don't have to.
Same engine. Opposite container.
Why you can trust it
Not promises we make. Things the device is built to be incapable of.
Every answer comes from the actual rule, with the citation shown. If the answer isn't in the rules it holds, it tells you so — it won't guess from memory.
No internet, no uploads, no syncing. The questions your desk asks stay on the device, in the building. There's nothing to intercept because nothing leaves.
Ask it to approve a loan or call a judgment and it hands the call back to you. It shows what the rules require. The decision stays with the banker — and the examiner sees a tool that knows its place.
The file never leaves
A credit file holds the most sensitive material a bank touches. So the device takes it the short way: straight from the machine on your desk to the device beside it. It never crosses the internet, never lands in a cloud, never sits on anyone else's server — because there's no connection for it to travel over.
The device reads what the work needs, keeps its answers encrypted and unlocked only by you, and holds no line to the outside world that anyone could reach down.
And the most sensitive papers never reach it at all. Tax returns stay on paper, keyed in by the underwriter the way they always have been. Credit reports move through the same regulated channel your bank already uses. The device works from the figures — it never holds the documents behind them.
The rules it keeps. The borrower's file it reads and lets go. The most sensitive papers it never sees at all.
— it's built to know what it shouldn't hold.
What it knows
Loaded with the federal and California rules a lending and compliance desk works under — each one checked against the official source, dated, and kept current. Need another state for the occasional out-of-area deal? It's a volume you add. And if an update ever lapses, the device keeps answering with the last version it has, clearly dated. It never goes dark.
Ask in plain English. Get the rule, the section, and the date it's good through.
The workflow
A credit moves through five stages before it's on the books. At every one, the assistant does the work around the decision — and leaves the decision to the bank.
It reads the file the way an analyst would — rent rolls, financials, entity papers, the appraisal — and pulls the figures that matter into one place. Nothing is uploaded anywhere; the reading happens on the device.
Does the intake. You confirm what's in the file.
It runs the math your credit policy defines — debt-service coverage, loan-to-value, cap-rate and stress cases, guarantor global cash flow — and shows each result against your bank's own thresholds, with the rule or policy line it's measuring against.
Does the arithmetic. You set the assumptions.
It drafts the credit memo from the facts already in the file — the numbers, the structure, the regulatory checkpoints, the exceptions that need a look — in your bank's format, with every figure traceable to its source.
Drafts from the facts. You write the recommendation.
It lays the file out for committee — what meets policy, what doesn't, what an examiner would ask — so the decision is made on a complete picture. It never casts a vote.
Assembles the case. The committee decides.
Once approved, it checks the closing and boarding file for completeness against the terms and the rules — the missed spousal joinder, the vesting that doesn't match, the threshold not documented — the gaps that surface years later in a workout.
Catches the gaps. You board a clean file.
It streamlines the work around the decision. It never makes the decision.
Owning it
The cloud charges by the question, because you're renting someone else's machine. This is a device your bank owns outright — consonant with the belief that an institution should own its infrastructure, not lease it.
No per-question billing. Hand it the long jobs overnight; it works on its own hardware and never sends a bill for the time.
It doesn't connect to your network or your core. Your IT team's only job is to confirm it's as sealed as we say — an afternoon, not a quarter.
No third party meters, logs, or reviews the questions your staff need to ask to do their work. What happens on the desk stays on the desk.
Private beta · by invitation
We'll show you the device answering the questions your desk asks every day — and refusing the ones it shouldn't.
Request a demo