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

Homeowners Claims — Playbook

Audience: Homeowners, insurers, adjusters, contractors, inspectors. Playbook Type: Scenario pack + Solve + Optimize loop Status: Soft (practice) — not yet LIVE Source: Claims Plane — Processing Claims, Guarded Transitions, and Declarative Packs §4 (home claims pack), D-09 — Optimization Capability (developer) §1.3 (procurement.consolidated_order@1)


1. Use & Purpose

Homeowners claims processing for property damage, theft, liability, and catastrophe — multi-party asset governance with expert sign-off. The playbook takes a home claim from loss notice to settlement, using solver-assisted contractor selection and escrow-backed payment, with expert sign-off required before any money moves.

Optimizers propose, claim gates authorize, never settle or pay.


2. Who Uses It

PlayerRole
HomeownerReports loss, provides evidence, receives settlement
AdjusterLoss assessment, approval
ContractorRepair execution, evidence upload
InspectorQuality verification, sign-off
InsurerRisk bearer, settlement payer
ReinsurerNotice for catastrophe/high-value claims

3. Flow

StepActorActionGate
1HomeownerLoss notice via broker/direct intakePhotos, police report (theft), authority report (fire)
2SystemClaim created: cns://claim/type/insurance/home_claim, PoCE session startedRequired fields validated; 400 if missing
3AdjusterAssigned via panel eligibility (two-person quorum for amounts > $500)SOD: adjuster ≠ contractor
4Solverprocurement.consolidated_order@1 recommends contractor + route compositeFail closed: solver down → 503
5Human adjusterApproves contractor + estimateNamed human confirms; expert sign-off mandatory
6ContractorPerforms repair, uploads completion evidenceEvidence: photos, arrival point, sign-off
7InspectorVerifies repair quality, signs offSOD: inspector ≠ contractor
8FinanceEscrow releases to contractor against verified prooffn::escrow::disburse against inspector sign-off
9SystemClaim finalized with PoCE receiptAll transitions recorded; receipt sealed

4. Guard Rails

  • Expert sign-off is mandatory. No path around it — no auto-certify, no auto-fine.
  • Two-person quorum for claim amounts above $500.
  • Solver verdicts are gates, not approvals. Never settles or pays.
  • Home lines demand photos and authority report as evidence.
  • No match means no assignment. fill_infeasible verdict if no qualified contractor available.
  • External verdicts honoured. Negative verdict blocks settlement.
  • Escrow releases only against verified proof. No cash handling.

5. Evidence & Rollout

ElementDetail
Version1.0.0 (Soft)
Source packHome claims (Kenya) — cns://claim/type/insurance/home_claim
CNS typescns://claim/type/insurance/home_claim, cns://resource/property
Lookup valuesGuard policies, quorum bands, SLA windows, panel roles, intake maps (NATS KV)
PoCE integrationfn::lifecycle::start_poce_session → record_poce_step → finalize_poce_session
Solver capabilityprocurement.consolidated_order@1, engine cope_composite (basket split + VROOM route)
Escrowfn::escrow::hold / fn::escrow::disburse / fn::escrow::rollback
Rollout pathSoft → pilot in single region → LIVE gate
Low-resource behaviorFNOL via WhatsApp/USSD/walk-in; contractor works from issued list; verification via supervisor tap or SMS code

Soft ≠ LIVE honesty: Nothing sets live_gate_met without REAL probe results. Env flags alone never count.


6. What We Do Not Build

  • No synthetic settlement. The solver never settles or pays; a named human approver confirms via PoCE.
  • No fake contractor matches. Unqualified providers are never shortlisted.
  • No synthetic "OPTIMAL" verdict. Solver down → 503 fail closed.
  • No fake metrics (e.g., "97% claims settled in 7 days"). Live data or honest empty states.
  • No catastrophe modeling replacement. Reinsurer notice and catastrophe screening are configured, not invented.