Semantic Debt Discovery Report #002 — How Many Meanings Does “Claim” Have?

This Discovery Report applies the same evidence framework as Discovery Report #001 to the most operationally loaded noun in insurance: claim. Across publicly available policy wordings, claims handbooks, reinsurance treaties and reserving guidelines, the term resolves to at least six distinct governed meanings.

Each meaning is internally correct in its source document. The problem is the absence of a registry that records which meaning applies where — so claims operations, finance, reinsurance, actuarial and regulatory reporting each rely on a different implicit definition of the same word.

The result is structural: KPIs disagree, reserves diverge, AI assistants triangulate over inconsistent meanings, and audit trails cannot be reconstructed without a human in the loop. This report makes that Semantic Debt visible for one term.

Why does the same simple question — “how many claims did we handle last quarter?” — produce different answers from claims operations, finance and reinsurance, even when every team is acting in good faith on the same data?

The answer is not data quality. The answer is that the word “claim” resolves to a different concept in each team’s working language, and no canonical record exists to reconcile them.

Across publicly available claims documentation, the word claim appears in patterns such as the following — each one resolving to a different concept:

“The claim arose on 14 March, when a fire damaged the insured premises.” — refers to the underlying incident: the Claim Event.

“A claim must be notified to the insurer within 14 days.” — refers to the formal act of reporting: the Claim Notification.

“Open the claim in the case management system and assign a handler.” — refers to the operational case record: the Claim File.

“The claim was paid on 7 May for €42,300.” — refers to the monetary settlement: the Claim Payment.

“The claim was recovered in full from the at-fault third party.” — refers to subrogation receipts: the Claim Recovery.

“The claim is reserved at €120,000 pending final adjustment.” — refers to the financial provision: the Claim Reserve.

Each sentence is well-formed insurance English. Each one trains a downstream reader — or a downstream model — on a slightly different definition of the same word.

From the evidence above, “claim” resolves to at least six distinct Meaning Spaces:

Claim Event — the underlying incident or occurrence that triggers cover.

Claim Notification — the formal act by which the loss is reported to the insurer, which starts contractual timelines.

Claim File — the case record opened in the claims management system, the unit of operational work.

Claim Payment — the monetary settlement made to the insured, the unit of financial outflow.

Claim Recovery — amounts recovered from third parties, reinsurers or salvage after payment.

Claim Reserve — the financial provision held against expected future payout on an open case.

Each is a legitimate, governable concept with a distinct owner — Operations, Customer Service, IT, Finance, Recoveries and Actuarial respectively. Treating them as one term is the root cause of contradictory claims reporting.

Drift on claim is not occasional — it is the default operating condition of an insurance enterprise. The same case moves through six departments, each of which uses the word claim to refer to whichever facet they own at that moment.

Operations counts claims by Event. Customer Service counts them by Notification. IT counts them by File. Finance counts them by Payment. Reinsurance counts them by Recovery. Actuarial counts them by Reserve movements. The same Tuesday afternoon produces six different “claim counts”.

The drift is invisible because every department is internally consistent. It becomes visible only when a report, a regulator, or an AI assistant tries to reason across them.

Every ungoverned meaning of claim is one unit of Semantic Debt. Six meanings means six units per term, per line of business, per jurisdiction, multiplied by every other ungoverned noun in claims operations (loss, reserve, recovery, settlement, payment).

The cost surfaces every quarter close, every regulatory return, every reinsurance settlement, every IFRS 17 reconciliation and every AI deployment in claims. It is paid in analyst time, audit time, and in decisions made on top of conflated definitions.

It is also the most concentrated form of Semantic Debt in the industry, because claim sits at the intersection of operational, financial, regulatory and customer-facing processes simultaneously.

No enterprise registry today records Claim Event, Claim Notification, Claim File, Claim Payment, Claim Recovery and Claim Reserve as six distinct, owner-accountable concepts under one surface term — with a resolution rule that says which one applies in which context.

Until that registry exists, every downstream consumer — analyst, regulator, AI assistant — has to infer the right meaning from context, every time. Inference at scale is exactly what produces drift, and drift on claim is exactly what produces contradictory disclosures.

The missing decision is not “what does claim mean?”. The missing decision is “which six (or more) governed concepts does the word claim resolve to in our organisation, and who owns each one?”.

Retrieval — A RAG system retrieves passages containing the word claim and treats them as comparable. They are not; they describe different concepts. The assistant answers confidently across categories that should not be combined.

Triage — A first-notice-of-loss copilot must decide whether a customer call has created a Claim Event, a Claim Notification, or merely an enquiry. Without governance the agent picks based on phrasing in the prompt, not on a governed rule.

Reserving Assistance — An AI tool suggesting reserve movements must distinguish the Reserve concept from the Payment concept. Conflation produces under- or over-reserving that surfaces directly in solvency reporting.

Agentic Workflows — An agent that closes claims must distinguish closing a File (operational), recording final Payment (financial) and releasing Reserve (actuarial). Each is a different governed action. Without Semantic Governance, “close the claim” is ambiguous instructions to a system that does not know which of three things to do.

One word. Six meanings. Zero governance. That is the size of the Semantic Debt sitting inside the single most operationally important noun in insurance.

Discovery Report #001 showed that the most-used customer-facing term, coverage, carries at least six meanings. This Discovery Report #002 shows that the most-used operational term, claim, carries at least six more. Together they are not edge cases — they are the central nouns the industry uses to describe what it does.

Semantic Governance is the discipline that retires this debt by recording each governed meaning, assigning an owner, versioning the definition and exposing it through a resolution API that humans, systems and AI agents can call. WikiSure is the platform that makes that discipline operational.