Insurance claim files
What it is: FACE’s cargo insurance evidence documents, and the general model when you ask questions about a file.
What it does
It assembles the cargo claim file for an adjuster, so the adjuster starts from the records rather than from a search. It never decides cover. Its jobs:
- First notice of loss. Builds the
FNOLdocument from the loss records, and names what hasn’t been stated. - Cargo loss survey. Sets out what was lost or damaged, and its value, from the records.
- Warranty compliance audit. Checks the shipment’s records against the warranty conditions the policy states, such as a temperature band.
- Recovery. Prepares the subrogation demand against the carrier.
What it reads
The policy records you hold (wording, warranties, declared value, deductible), certificates, loss reports, temperature and custody records, carrier contracts and the claim’s own documents.
What it produces
Evidence documents FNOL, CARGO_LOSS_SURVEY, WARRANTY_COMPLIANCE_AUDIT and
SUBROGATION_DEMAND, each attached to an action card with one proposed next step. The
cards wait on Actionable Twins; the FNOL, survey and subrogation cards sit under
the claims play.
Every fact cites the record it came from, and a missing figure is recorded as absent
with a reason. See Evidence documents.
Human oversight
- The adjuster, or another person with authority, decides. The agent never underwrites, prices a risk, accepts or declines cover, sets a reserve or settles a claim.
- No finding code says
VOID,DECLINED,REPUDIATEDor anything like it. Those are an underwriter’s words. - Approving a card seals its document and records who approved it.
Model
The documents on this card are built by fixed arithmetic over cited records. No model is involved in them. A model may phrase a document’s narrative only after its figures are set.
Questions you ask about a file in free text go to the general reasoning tier.
Where it runs and data handling
On the deployment’s own model plane: Runink’s shared machines on a Trial, your own cloud on Cloud and your own servers on On-premises. No outside AI service is called on any plan. See Facts shared by every card.
Guardrails
The documents are built to these policies:
- Never invents a warranty condition the policy doesn’t state, for example a temperature band inferred from the word “reefer”.
- Never reads a missing declared value as zero, and never substitutes an invoiced value for an undeclared one.
- Never states that something caused a loss unless the records say so. A temperature reading and a crushed carton are two facts, not a cause and an effect.
- Never leaves out a loss figure the records state, and never discourages a claim.
- Never treats protected characteristics, or postcode and nationality as proxies for them, as grounds for anything.
How to read its results
- A document is a file, not a decision. It doesn’t establish that a loss is or isn’t covered.
- It works from the records you hold.
- FACE’s approval tiers govern who may approve an action inside FACE; a claim handler’s delegated authority stays with your own process (see Auditability & lineage).
- A free-text answer from the general model is the model’s reading of the file, not a document. Check it against the cited records.