JJijibora
Docs & Product Guide
On this page (12 sections)

Insurance Claims — Implementation Guide

Audience: Insurers, reinsurers, brokers, TPAs, implementation teams. Vertical: Insurance — motor, home, liability, catastrophe claims. Status: Configuration-only design; seeded Kenya insurance packs (motor, medical, home); no bespoke tables. Substrate: Reuses Jijibora community sourcing scenario, building reflex, and Kenya claim routing seed.


1. Claim Types — Insurance

Claim TypeCNS URIBound ToTypical Evidence Required
Motor Claimcns://claim/type/insurance/motor_claimresource:vehicleLoss notice, adjuster report, garage estimate, police report, photos
Home Claimcns://claim/type/insurance/home_claimresource:propertyLoss notice, adjuster report, repair estimates, photos, authority report
Liability Claimcns://claim/type/insurance/liability_claimtruth_node:personIncident report, witness statements, legal evidence, adjuster report
Catastrophe Claimcns://claim/type/insurance/catastrophe_claimresource:policyLoss notice, reinsurer notice, catastrophe modeling, mass adjuster deployment

2. Provider Panel — Insurance

Insurance claims use a provider panel with four roles (broker, adjuster, garage, reinsurer). Panel membership composes canonical organisation, capability, and attestation records.

RoleCapabilities RequiredAttestationLease TTLClaim Types
Brokerrecognised_intake, distribution, policy_placementYes1 hourAll (first notice of loss)
Adjusteradjustment, loss_assessment, claims_reviewYes1 hourMotor, home, liability
Garagemotor_body_repair, glass_repair, paint_workYes1 hourMotor
Reinsurerreinsurance, evidence_review, catastrophe_screeningYes8 hoursMotor, home, liability, catastrophe

All roles require: approved affiliation + active status + attestation. Fail-closed: missing values refuse with a service error.


3. Guard Policies — Insurance

3.1 Separation of Duties

Claim TypeCreator May Approve?Barred PairsNotes
Motor ClaimNoAdjuster ↔ GarageAdjuster assesses; garage repairs — different persons
Home ClaimNoAdjuster ↔ ContractorSame as motor
Liability ClaimNoClaimant ↔ AdjusterDifferent parties
CatastropheNoAdjuster ↔ ReinsurerDifferent entities

3.2 Quorum Bands

Amount RangeRiskQuorumApprover Roles
Small amountLowOne-person standardAdjuster
Mid amountMidTwo-personAdjuster + reinsurer
Large amountHighThree-personAdjuster + reinsurer + senior adjuster
LitigationAnyCross-agencyLegal + external auditor + reinsurer

High-risk motor claims need three approvals; large amounts need two; mid standard amounts need two; mid low amounts and small amounts need one.

3.3 Evidence Requirements

Claim TypeRequired EvidenceSource
Motor ClaimLoss notice, adjuster report, garage estimate, police report, photosIntake + adjuster + garage
Home ClaimLoss notice, adjuster report, repair estimates, photos, authority reportIntake + adjuster + authority
Liability ClaimIncident report, witness statements, legal evidence, adjuster reportLegal + adjuster
Catastrophe ClaimLoss notice, reinsurer notice, catastrophe modeling, mass adjuster deploymentIntake + reinsurer + modeling

4. SLA Windows — Insurance

Claim TypeSeverityDefault WindowEscalation To
MotorUrgentShort (24-48 hours)Adjuster
MotorStandardWide acceptance windowAdjuster
HomeUrgentShortAdjuster
HomeStandardWideAdjuster
LiabilityLitigationLongestReinsurer
CatastropheAnyMass deployment windowReinsurer

Windows are values per type and severity, bound to the same workflow flow and namespace. Urgent motor and property windows are short; litigation windows are longest.


5. Intake Maps — Insurance

Map IDTargetFields MappedSource Channels
intake:insurance:motorclaim creationpolicy_id, vehicle_id, loss_type, loss_date, location, photos, police_refBroker, API, walk-in, API
intake:insurance:homeclaim creationpolicy_id, property_id, loss_type, loss_date, photos, authority_refBroker, API, walk-in
intake:insurance:liabilityclaim creationpolicy_id, claimant_id, incident_type, description, witness_refBroker, legal, API
intake:insurance:catastropheclaim creationpolicy_id, event_type, affected_area, mass_deploy_refReinsurer notice, catastrophe desk

Intake plus four provider maps for motor; intake plus two provider maps for medical; intake plus three provider maps for home; intake only for government benefit/compensation; intake only for community tickets.


6. PoCE Integration Points

TransitionPoCE TriggerEvidence Recorded
First notice of lossfn::lifecycle::start_poce_sessionpolicyholder, vehicle/property, loss type, location
Adjuster assessmentfn::lifecycle::record_poce_stepadjuster, findings, estimate, reserve
Garage repairfn::lifecycle::record_poce_stepgarage, repair work, parts, completion
Claim settledfn::lifecycle::finalize_poce_sessioninsurer, amount, payment reference, reinsurer notice
Litigationfn::lifecycle::record_poce_steplegal counsel, court filing, settlement

7. Worked Example — Motor Claim (Kenya)

  1. Broker files FNOL — vehicle accident reported via broker intake.
  2. Claim created: cns://claim/type/insurance/motor_claim, bound to resource:vehicle, identity attestation required at FNOL, PoCE session started.
  3. Adjuster assigned via panel (two-person quorum for standard amounts).
  4. Loss assessed — adjuster inspects vehicle, reviews police report, gets garage estimate.
  5. Garage assigned via sourcing bus (qualified, nearest, certified), quote approved.
  6. Repair completed — garage performs work, uploads completion evidence.
  7. Claim settled — insurer pays against verified repair proof, reinsurer notified.
  8. Claim finalized with PoCE receipt: broker → adjuster → garage → insurer settlement chain.

Guard check: Adjuster ≠ Garage (SOD enforced). Litigation evidence preserved. Negative outside verdict blocks settlement.


8. What We Do Not Build

  • No insurer replacement. Insurers remain the risk bearer and policy system of record; Sovereign OS adds governed claims processing and audit.
  • No synthetic "optimal" settlement amount. Solver down → 502/503 fail closed.
  • No fake metrics (e.g., "95% claims auto-settled"). Live data or honest empty states.
  • No advance without PoCE. AI help is advice only; never advances governance.

9. Deployment

  1. Deploy strata: s282_processing_claim, s214_claim_arbitration, s210_claim_validation_registry
  2. Seed CNS types: cns://claim/type/insurance/*
  3. Seed lookups: guard policies, quorum bands, SLA windows, panel roles, intake maps in NATS KV
  4. Seed scenario packs: motor, home, liability, catastrophe packs (Kenya)
  5. Configure panel: broker/adjuster/garage/reinsurer roles in NATS KV
  6. Test: GET /v1/claims/processing/readiness — all probes must pass before LIVE