Technical overview for engineering, claims operations and AI-assisted due diligence. The following describes the laboratory workflow and pilot scope.
What it is.
A receipt system between companies, with a neutral seal and a rulebook: the system records evidence and prepares the case; a person decides; every step has a receipt a regulator or an auditor can verify with a public program.
Status: laboratory implementation tested with synthetic cases, reported 25 October 2026. Real-scan evaluation and customer-data testing remain pilot work. Recovery netting has been tested as a laboratory pattern, not as a connected insurer production service.
What it does
01 · READS
The papers become one case
The claim form, the accident report, the photos, the repairer's estimate or invoice: an AI reader fills a fixed form — policy, vehicle, date, place, items, flags — and says how sure it is of each field. It reads; it never decides.
02 · CHECKS
Checklist, cover, arithmetic — by rule
Is every required document there (a police report above the threshold)? Was the policy active that day, the peril covered, no exclusion triggered? Each item against your price list, minus the deductible, inside the limit. The same facts always give the same answer; no model inside.
03 · GATES
Checks against configured limits
A mathematical gate in front of every decision: the limit per claim and per day, the covered products, the counterparties. What is outside is refused before any work, with a record naming the policy version.
04 · CONFIRMS
One click by your adjuster
The adjuster sees the prepared case — the arithmetic shown, the confidences, the documents' receipts — and confirms, in full or by sampling as you choose. If a document is missing, the letter to the customer is already written: it lists exactly what is missing.
05 · PROVES
A receipt for every step
Every document and every decision leaves a 32-byte fingerprint on a neutral, sealed ledger; document processing runs on the infrastructure agreed for the pilot. Anyone with the public keys verifies a receipt offline. At month end you get an evidence file for every claim — record-keeping with proof, not a claim of compliance.
06 · RECOVERS
Recoveries between insurers, with proof
Where another party is liable, the recovery notice is prepared with a verifiable evidence bundle. When the other insurer connects its own ledger, both record the same event, objections run on a clock, a person rules, and positions net daily. Until then the notice leaves by the old road — better documented.
A claim, from the inbox to the confirmed case
1
Your inbox · automatic
Receive
The documents arrive; each one's fingerprint is recorded at your own ledger within a minute — evidence before anyone decides.
2
The reader · prepares
Read
The AI fills the case form and attaches a confidence to every field. Structural checks run: sums add up, dates in order, the policy number's form.
3
The rules · decide what is checkable
Check
Completeness, cover, exclusions, the arithmetic against your price list. Missing document → the customer's letter. Over the limit → the adjuster's file, not the line's.
4
Your adjuster · decides
Confirm
One click on a prepared case; the confirmation is itself a record. Where you have written a machine-checkable condition into your terms, the rule decides.
5
Month end · automatic
Evidence
An evidence file for the month, verifiable with the public program; recoveries listed with their bundles.
Who decides what
The machine proves; people judge
The rule — your terms, versioned, accepted.
The check — yes or no, the same answer for the same facts.
The reader — prepares and says how sure it is; never decides.
The person — confirms, signs; the only step that can bind.
The appeal — a new decision, never an edit.
From the laboratory
What ran on 25 October 2026
On our own machines: a synthetic glass claim — three documents fingerprinted at the insurer's ledger, 480 € capped to 450 by the price list, 55 € labour, 100 € deductible, 405.00 € approved, offered, ordered under a 1,000 €-per-claim mandate, accepted with the arithmetic shown, confirmed by the adjuster. The same day, a three-party recovery lab (operator, insurer, supplier) ran five scenarios to their rule-given ends with two rulings and two test settlements. Synthetic cases; no insurer's data; test units.
How to start
Ten cases, two weeks, one machine
Give us ten anonymised real cases — clean ones, refused ones, recoveries. They are processed only on machines we or you control; data handling and permitted services are agreed before the pilot. In two weeks we return them as prepared cases with the reading-error rate on your forms, the arithmetic and a month-end evidence file. Then a paid pilot: one machine in your network or ours, your terms as the rules, your adjusters confirming.
Boundaries
What we say and do not say
Evidence-supported record-keeping; "compliant" is the regulator's word, not ours.
"Verified" means the receipt verifies — not that a decision was right.
A person confirms every payout; one touch on a prepared case, not zero-touch.
Your data stays yours: fingerprints travel, documents do not.
This browser example uses synthetic amounts from the published glass-claim scenario. It runs locally on this page. The live document reader, policy checker and evidence verification are separate parts of the private pilot.