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

Construction Claims — Implementation Guide

Audience: Developers, contractors, inspectors, implementation teams. Vertical: Construction — building projects, infrastructure, milestone payments, defect rectification. Status: Configuration-only design; expert sign-off gates; no bespoke tables. Substrate: Reuses Jijibora building safety inspections scenario (7-stage chain) and building reflex.


1. Claim Types — Construction

Claim TypeCNS URIBound ToTypical Evidence Required
Project Delay Claimcns://claim/type/construction/project_delayresource:projectSchedule baseline, delay notice, force majeure evidence, impact assessment
Milestone Payment Disputecns://claim/type/construction/milestone_paymentclaim:paymentMilestone certificate, work evidence, payment application, certification
Defect Rectification Claimcns://claim/type/construction/defect_rectificationresource:buildingDefect list, inspection report, rectification evidence, sign-off
Insurance Claimcns://claim/type/construction/insurance_claimresource:policyLoss notice, adjuster report, repair estimates, reinsurer notice
Handover Claimcns://claim/type/construction/handoverresource:buildingHandover certificate, defect punch list, occupancy permit

2. Expert Sign-Off Gate

Construction claims follow the building safety inspection scenario pattern (7-stage chain):

  1. Scheduled → 2. Evidence recorded → 3. Expert sign-off → 4. Certificate issued → 5. Packet exported → 6. Expiry watch → 7. Re-inspection

Expert sign-off is mandatory — no path around it. No auto-certify, no auto-fine. Event names are provisional until registration.


3. Guard Policies — Construction

3.1 Separation of Duties

Claim TypeCreator May Approve?Barred PairsNotes
Project DelayNoContractor ↔ OwnerDifferent parties; owner certifies delay
Milestone PaymentNoContractor ↔ CertifierContractor performs work; certifier certifies — different persons
Defect RectificationNoInspector ↔ ContractorInspector certifies fix; contractor performs fix
Insurance ClaimNoClaimant ↔ AdjusterDifferent parties
HandoverNoDeveloper ↔ InspectorDifferent parties; inspector certifies building

3.2 Quorum Bands

Amount RangeRiskQuorumApprover Roles
< KES 1MLowOne-person standardProject inspector
KES 1M – 10MMidTwo-personInspector + project manager
> KES 10MHighThree-personInspector + project manager + developer
InsuranceAnyReinsurer noticeAdjuster + reinsurer

3.3 Evidence Requirements

Claim TypeRequired EvidenceSource
Project DelaySchedule baseline, delay notice, impact evidenceProject management system + schedule
Milestone PaymentMilestone certificate, work evidence, payment applicationPayment application + certification
Defect RectificationDefect list, inspection report, rectification evidenceBuilding inspection + contractor fix evidence
Insurance ClaimLoss notice, adjuster report, repair estimatesInsurance system + adjuster
HandoverHandover certificate, defect punch list, occupancy permitBuilding safety inspection + occupancy permit

4. Panel Roles — Construction

RoleCapabilities RequiredAttestationLease TTLClaim Types
Project Inspectorloss_assessment, snag_inspection, safety_certificationYes1 hourAll
Project Managermilestone_certify, schedule_approve, progress_reviewYes8 hoursDelay, milestone, handover
Contractorconstruction_repair, defect_rectify, work_completeYes1 hourDefect rectification
Developer Representativetitle_verification, handover_approve, sale_approveYes8 hoursHandover, warranty
Adjusterloss_adjustment, repair_estimate, reinsurer_noticeYes8 hoursInsurance claim
Reinsurerreinsurance_notice, catastrophe_screeningYes8 hoursInsurance claim

5. SLA Windows — Construction

Claim TypeSeverityDefault WindowEscalation To
Project DelayStandard30 daysProject manager
Milestone PaymentStandard14 daysProject manager + finance
Defect RectificationUrgent48 hours (safety-critical)Project inspector
Defect RectificationStandard30 daysProject inspector
Insurance ClaimStandard90 daysAdjuster + reinsurer
HandoverStandard60 daysDeveloper representative

6. Intake Maps — Construction

Map IDTargetFields MappedSource Channels
intake:construction:delayclaim creationproject_id, delay_type, delay_days, force_majeure, impact_assessmentProject management, site report
intake:construction:milestoneclaim creationproject_id, milestone_id, work_evidence, payment_application, certificate_refPayment application system
intake:construction:defectclaim creationbuilding_id, defect_list, severity, inspector_id, locationBuilding inspection, snag list
intake:construction:insuranceclaim creationpolicy_id, loss_type, loss_notice, adjuster_ref, repair_estimatesInsurance system, adjuster

7. PoCE Integration Points

TransitionPoCE TriggerEvidence Recorded
Delay noticefn::lifecycle::start_poce_sessionproject, delay type, impact, schedule baseline
Milestone certifiedfn::lifecycle::record_poce_stepcertifier, milestone, work evidence, payment app
Defect foundfn::lifecycle::start_poce_sessionbuilding, defect list, inspector, location
Defect rectifiedfn::lifecycle::record_poce_stepcontractor, rectification evidence, completion photo
Defect signed offfn::lifecycle::record_poce_stepinspector sign-off, handover readiness
Insurance lossfn::lifecycle::start_poce_sessionpolicy, loss type, adjuster, estimates
Handover completedfn::lifecycle::finalize_poce_sessiondeveloper, occupancy permit, defect punch list

8. Worked Example — Milestone Payment Dispute

  1. Contractor submits milestone payment application for foundation work completed.
  2. Claim created: cns://claim/type/construction/milestone_payment, bound to claim:payment, PoCE session started.
  3. Project inspector assigned via panel (two-person quorum for amounts > KES 1M).
  4. Work evidence reviewed — photos, GPS timestamps, material deliveries, labor hours.
  5. Milestone certified — inspector + project manager sign off (quorum reached).
  6. Payment authorized — funds released from escrow against verified proof.
  7. Claim finalized with PoCE receipt: contractor → inspector → project manager → escrow release chain.

Guard check: Contractor ≠ Certifier (SOD enforced). No payment without milestone certificate (expert sign-off). Escrow releases only against verified proof.


9. What We Do Not Build

  • No project management replacement. Project management tools remain the system of record for schedules; Sovereign OS mirrors milestone and delay data.
  • No construction cost estimation engine. Unless expressible as solver-gateway capability + declarative lookups.
  • No synthetic "optimal" crew allocation. Solver down → 502/503 fail closed.
  • No fake metrics (e.g., "97% on-time completion rate"). Live data or honest empty states.

10. Deployment

  1. Deploy strata: s128 (Mayet FSM), s151 (Pipeline FSM), s282_processing_claim, s214_claim_arbitration
  2. Seed CNS types: cns://claim/type/construction/*
  3. Seed lookups: guard policies, quorum bands, SLA windows, panel roles, intake maps in NATS KV
  4. Seed scenario packs: project delay, milestone payment, defect rectification, insurance claim packs
  5. Configure expert sign-off gates per claim type
  6. Test: GET /v1/claims/processing/readiness — all probes must pass before LIVE