Pay a claimRefused
£48,500.00
Above the handler’s authority. Never executed: no clawback, no recovery, no difficult call. The refusal is the record.
Insurance, governed at the action.
Underwriting, claims, reinsurance, bordereaux and regulatory reporting. One spine runs beneath all of them: the same kernel that governs the rest of the platform, deciding allow, hold or refuse before anything executes.
Coverage
What it covers. The workflows an insurance business runs on, and the moment in each that costs money.
Broker intake
Broker submissions arrive by API or by email and land in an underwriting queue.
A submission is the first thing an underwriter answers for. It belongs in a queue, not an inbox.
Quote and bind
AI assistants can quote and hand off binds through a governed tool interface, with every dispatch recorded.
A bind is the moment cover exists and the balance sheet moves. Nothing should reach it unchecked.
Claims
A claim payment moves money on somebody’s authority. The worked example below follows one that tries to go beyond it.
Reinsurance
Cessions and recoveries are obligations between carriers. Who did what, on whose authority, on what basis: the record matters on both sides of the treaty.
Bordereaux
Delegated authority business, in the Lloyd’s market and elsewhere, reports through bordereaux, and the parties on each side carry obligations tied to what those files say.
Regulatory reporting
A return is a statement about what the business did. The shorter the distance between the working record and the return, the fewer reconciliations stand between them.
Worked example
A payment above authority. The same handler, twice, ten minutes apart. And a bind that waits.
An assistant working a motor claim proposes a settlement payment. The handler it acts for holds authority to £25,000. The kernel checks the action before it executes, and an action that fails its checks does not execute.
Pay a claimAllowed
£18,400.00
Inside authority, ten minutes later. The checks pass and the payment is sealed in a signed record.
Bind a riskHeld
A person decides
A bind is the moment cover exists. It waits for a named person, and resumes as exactly what was approved.
Synthetic scenario, in the shape the kernel records a decision. No live data.
Refused
A record of the refusal, with the reason it was refused.
The payment never happened. What exists instead is the record.
Allowed
The action is sealed in a signed, tamper-evident record.
Replay the same proposal and the answer does not drift.
Held
An action held for approval resumes by replaying only what was approved — nothing else.
Some actions deserve a person rather than a verdict.
Underneath
The spine is the kernel. Insurance OS is not a separate product with its own idea of governance.
The rules live in a pack
An industry is a configuration file, not a codebase. The rules of insurance, authorities, limits, the actions that need a person, live in an industry pack the governance layer loads.
Checked at every boot
The pack is load-bearing: at boot the governance layer recomputes the pack's rule digest and refuses to serve if it does not match.
A pack that fails verification means the system does not start, not that it starts leniently.
The same discipline, everywhere on the desk
- Same input, same verdict, every time.
- When the kernel cannot decide, it refuses — an unclear case is never waved through.
- Agents run under quotas and spend caps, with human approval gates on the actions that matter, and over a quarter those records accumulate into something you can hand over.
- The evidence a period produces can be given to a third party and verified with Admissible absent.
Start here
Bring one workflow
A payment, a bind, a bordereau: one place where an AI action worries you. We will show you the verdict it gets, and the record it leaves.