Built for the payment you should not make.
This page states the rule we hold ourselves to, the controls the kernel enforces, and what is not finished.
No live bank or payment credential enters Regent until every high-severity security finding is closed.
In the pilot Regent is read-only. It never pays, posts or emails anyone.
These hold whatever the AI proposes. They are code in the database and the kernel, not instructions to the AI.
Money only goes to verified accounts
The kernel refuses any payment to a bank account that hasn’t been verified. A changed account starts unverified, in a cooling-off period, until a call to the phone number already on file confirms it.
No one approves their own work
The person responsible for an AI agent can’t sign off that agent’s requests. Someone else has to.
Nothing is erased
Entries are never edited or deleted. A correction is a reversing entry, so the history always reads true.
Every change is rehearsed first
The kernel shows the exact journal lines before anything is recorded, and a person signs off on those lines.
Rules live with the money
Limits, approval rules and double-entry balance are enforced in the database, not by the AI.
Better you read it here than find out later.
- Per-person sign-in is being added.
- Filings stay drafts until an accountant verifies the rules.
- No AI agent acts beyond shadow mode until an open issue with agent permissions is fixed.
- Regent has not run on a real business’s books yet.
Our simulator keeps its own set of reference books, written without any Regent code. Regent’s trial balance has to match them to the penny. In simulation it does, across 10 business areas. That is a simulation result, not a customer result.
The simulator also plants 70 kinds of labelled fault on purpose, so every catch and every miss is scored.
Pilots will use a hosted AI model service until our own model can run on the pilot computer. So the text of a bill or vendor email, and the fields around it, goes to a provider we name in writing before your pilot starts. The ledger, requests and sign-offs stay on the pilot computer. Updates come down and a health check goes up. No bank or payment login is connected during the pilot.
We train Grogan Development Group’s own models on our own usage and simulations only. No model has been released.
- Now: our own usage and our simulations only.
- Pilot data, later: only if you opt in, in writing.
- Never: pilot data without that opt-in, and no scraped data.
- Messages sent through the forms on this site are not used for training.
Regent is open source. Read the code, run it, and check what the kernel does with your own eyes. Commercial licensing is available on request.
github.com/Grogan-Development/regentAsk about anything on this page.
If you look after the money or the computers, you should get straight answers. Write to us.