A claim resumes when the report arrives. Not when somebody remembers.
A claim spends most of its life waiting. Make that waiting a durable process instead of a diary note and somebody’s memory.
The systems you already run, the objects your product declares, and the work your team gets back.
These marks name the kinds of system a source declaration reaches — a picture of the ecosystem, not a fixed menu, and nothing here implies a partnership.
Nothing waits on a memory. Nothing pays unreviewed.
The diary note becomes a process
A claim waiting on an adjuster’s report is a Workflow paused there, resuming when the report arrives.
One claim file, not five systems
Policy terms, reserves, payments and documents become one object, each figure naming the system behind it.
Review where money moves
A payment above your authority limit parks until a second person approves the amount and its reserve.
What teams build. On day one.
Four places this work turns into declared objects, governed reads, and reviewed changes.
Claim file
A Function assembles cover, reserves, payments, documents and correspondence into the file a handler otherwise rebuilds screen by screen.
Coverage check
Coverage as of the loss date is one declared Function, not a rule each handler learned separately and applies slightly differently.
Settlement authority
An offer over a handler’s limit is an Action that parks, showing the approver the amount, the reserve effect and the basis before release.
Endorsement
A mid-term change is one reviewed Action showing its effect on cover and premium, not edits typed into two systems separately.
How it runs. End to end.
The same path every product takes: connect what exists, declare what it means, then publish the reads and the changes.
- 01
Connect policy, claims and billing, and write to none of them
Each stays where it is; Bijection holds a read credential and takes a copy at the interval you set. A handler can say when the reserve or the payment history was last read, rather than assume it is current.
- 02
Declare the product you actually sell
Policy, cover, insured, claim, reserve, payment. Bijection ships no insurance product; a declaration makes one, and a different declaration makes something that is not insurance at all.
- 03
Give the long waits somewhere to live
First notification of loss through settlement is a durable Workflow. It holds at a declared step for the report, the document or the third party, resumes when that lands, and records each step it took.
- 04
Let agents prepare, and people decide
An agent can assemble the file and draft the next step through the same Functions a handler uses. Applying anything crosses an Action, under authority never wider than the handler who delegated it.
Common questions.
No. It stays the system of record and Bijection only reads it. What changes is that a question spanning policy, claim, billing and documents has one answer with its sources attached, and that the operational changes around it cross declared Actions instead of four separate screens.
You can show what was done: which Action executed, who authored it, the authority they held, what it read, the effects it applied and who approved it, in an append-only record. That is evidence about an operation, not a certification. Nothing here makes you compliant, and whether this evidence satisfies a particular obligation is your control owners’ judgement, not ours.
Not on its own in this design. Inference is a declared step inside a Function, and an agent proposes rather than applies: a declared Action makes the change, under whatever review you set. If you want an outcome applied with nobody in the loop, that is you declaring an Action without a review rule. The platform will not make that choice for you.
Bring us a process.
We'll build it with you.
A business process, the systems it touches, and the rules it needs to follow.