Insurance claims · Flagship - built
The decision: Pay or investigate
A motor damage claim with a repairer invoice, photographs, a medical certificate and six weeks of correspondence. Nothing in it is obviously wrong. The examination is not looking for something obviously wrong.
There is no production tenant and no paying customer. Every document, finding and verdict on this page is synthetic, written to show what the forensic core examines and what a cited verdict looks like. No accuracy or detection figure appears here, because no pilot has produced one under a methodology we would publish beside it. The insurance rule set behind this example is built and tested; every rule ships marked unverified until a named person has checked it against the primary instrument.
The bundle as it lands, before anybody has read it.
The forensic core runs on every document in the bundle regardless of sector. None of these questions changes when the industry changes.
Every finding carries at least two anchors drawn from at least two separate documents, and the benign explanation that would account for it. A pattern appearing once in one place is not reported at all.
The same repairer, the same eighteen part numbers in the same order, at the same unit prices, on a claim closed four months earlier for a different policyholder and a different vehicle. The totals differ; the line items do not.
The benign explanation: A repairer with a standard parts kit for a common collision type would produce similar invoices legitimately, and some workshops do template their quotes.
Embedded capture metadata on three of the eleven images predates the incident date on the claim form by nine days. The remaining eight are consistent.
The benign explanation: Camera clocks are frequently wrong, and images forwarded through messaging applications can carry the metadata of an earlier file entirely.
The clock started on receipt of the last outstanding information. Under the applicable code the decision is due within the encoded period, counted in business days under this state’s calendar, and a public holiday falls inside the window.
The benign explanation: Not an integrity matter at all. It appears in the same verdict because the same file drives both, and because a decision made late is a breach whether or not the claim was sound.
Two independent integrity findings, each anchored to two documents, plus an obligation expiring inside the working week. The file is referred to a person with the reasons attached and the source pages linked.
The platform has not declined the claim, has not flagged the claimant, and has produced no score. It has produced a position that a claims officer can act on and, if challenged, defend line by line.
The same four constraints apply in every sector, and they are enforced in code rather than in policy.
Nothing was declined, refused, held or approved by the platform. A person decides, on the record, with the reasoning in front of them.
Every sector
No risk number, no ranking, no composite figure. The only number attached to a person is how many independent documents corroborate a fact about them.
Nowhere in the product
Two anchors from two documents, or the finding is not reported. This is the largest source of false positives in the category and the platform refuses to generate them.
Enforced at registration
A detector referencing a protected attribute fails registration and the platform will not start. It is a structural guarantee rather than a policy.
Throws on load
Hand us two hundred closed files. Settled claims, funded loans, granted applications, paid invoices, onboarded accounts. We examine them and show you the documents that lied, against outcomes you already know. It is the only honest way to evaluate this category, and it is the same motion in every sector on this page.
Only insurance is built. Every other sector is specified rather than shipped: the forensic core runs on any bundle today, and no rule set outside insurance has been encoded. [email protected]