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

Real Estate Claims — Implementation Guide

Audience: Property developers, HOA boards, property managers, implementation teams. Vertical: Real Estate Development — large residential complexes, master-planned communities, apartment buildings, villa estates, retirement/lifestyle estates. Status: Configuration-only design; no bespoke tables, no schema changes. Substrate: Reuses Jijibora building/reflex/community infrastructure (see Jijibora Tie-In in the real estate doc set).


1. Claim Types — Real Estate

Claim TypeCNS URIBound ToTypical Evidence Required
Defect / Snag Reportcns://claim/type/real-estate/defectresource:unitPhoto, arrival point, inspector sign-off, contractor ID
Service Charge Disputecns://claim/type/real-estate/service-chargeclaim:service-chargeInvoice, payment reference, lease terms, HOA board resolution
Construction Warranty Claimcns://claim/type/real-estate/warrantyresource:unitHandover certificate, defect list, contractor fix evidence, expiry date
HOA Assessment Disputecns://claim/type/real-estate/hoa-assessmentclaim:governance/resolutionVote record, BBS+ proof, resolution text, owner objection
Amenity Booking Disputecns://claim/type/real-estate/amenity-bookingresource:common-areaBooking confirmation, time slot, access log, cancellation policy
Lease / Tenancy Disputecns://claim/type/real-estate/leaseclaim:leaseLease agreement, rent payment history, notice to vacate, inspection report
Off-Plan Sale Claimcns://claim/type/real-estate/saleresource:unitSale agreement, payment schedule, handover certificate, title reference

2. Guard Policies — Real Estate

All guard policies are declarative values loaded from NATS KV (SOVEREIGN_LOOKUPS). No hardcoded per-type stage lists.

2.1 Separation of Duties (SOD)

Claim TypeCreator May Approve?Barred PairsNotes
Defect / SnagNoInspector ↔ ContractorInspector certifies fix; contractor performs fix — different persons
Service ChargeNoIssuer ↔ CollectorCharge issuer and payment collector must be different
WarrantyNoInspector ↔ ContractorSame as defect
HOA AssessmentNoVoter ↔ Resolution AuthorOwner who proposed resolution cannot be sole approver of objection
Amenity BookingYes (lenient)—Community ticket pattern; creator may approve
Lease DisputeNoLandlord ↔ TenantDifferent parties; property manager mediates
Off-Plan SaleNoDeveloper ↔ BuyerTitle transfer requires independent verification

2.2 Quorum Bands (Amount × Risk → Named Quorum)

Amount RangeRiskQuorumApprover Roles
< KES 50,000LowOne-person standardProperty manager
KES 50,000 – 500,000MidTwo-personProperty manager + HOA board member
> KES 500,000HighThree-personProperty manager + HOA board + developer representative
LitigationAnyCross-agencyLegal counsel + external adjuster + board

2.3 Evidence Requirements

Claim TypeRequired EvidenceSource
Defect / SnagPhoto (timestamped), arrival point (GPS), inspector sign-offMinIO storage + PoCE receipt
Service ChargeInvoice, lease terms, payment referenceERPNext integration + claim record
WarrantyHandover certificate, defect list, contractor fix evidenceBuilding safety inspection scenario
HOA AssessmentVote record, BBS+ proof, resolution textCommunity governance (s165) + PoCE
Amenity BookingBooking confirmation, access logMall tenancy booking pattern
Lease DisputeLease agreement, rent history, inspection reportLease register (append-only)
Off-Plan SaleSale agreement, payment schedule, title referenceLand registry mirror (integration_entity)

3. Panel Roles — Real Estate

RoleCapabilities RequiredAttestationLease TTLClaim Types
Property Managerintake, distribution, maintenance_coordinationYes1 hourAll
HOA Board Membergovernance_vote, rule_enforcement, service_charge_approveYes8 hoursService charge, HOA assessment
Contractormotor_body_repair, defect_rectification, construction_repairYes1 hourDefect, warranty
Inspectorloss_assessment, snag_inspection, safety_certificationYes1 hourDefect, warranty
Developer Representativetitle_verification, handover_certificate, sale_approveYes8 hoursOff-plan sale, warranty
External Adjusterloss_adjustment, litigation_evidenceYes8 hoursHigh-value defects, litigation

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


4. SLA Windows — Real Estate

Claim TypeSeverityDefault WindowEscalation To
Defect / SnagUrgent48 hoursProperty manager
Defect / SnagStandard7 daysHOA board
Service ChargeStandard30 daysHOA board + finance
WarrantyStandard12 months (defects liability period)Developer
HOA AssessmentStandard14 daysHOA board
Amenity BookingStandard24 hoursProperty manager
Lease DisputeStandard30 daysProperty manager + legal
Off-Plan SaleStandard90 daysDeveloper representative

Windows are values per type and severity, bound to the same workflow flow and namespace. Missing values refuse with a service error.


5. Intake Maps — Real Estate

Map IDTargetFields MappedSource Channels
intake:real-estate:defectclaim creationunit_id, defect_type, description, photo_urls, severity, reported_byWhatsApp, USSD, walk-in desk, API
intake:real-estate:service-chargeclaim creationunit_id, charge_period, amount, invoice_ref, disputed_byERPNext, resident portal, walk-in
intake:real-estate:warrantyclaim creationunit_id, handover_date, defect_list, contractor_idDeveloper handover, inspector
intake:real-estate:hoa-assessmentclaim creationresolution_id, voter_id, objection_reason, vote_proofHOA meeting, AGM, portal

Intake maps target claim creation only; any other target refuses. Preview validates against the target contract read-only.


6. PoCE Integration Points

TransitionPoCE TriggerEvidence Recorded
Defect reportedfn::lifecycle::start_poce_sessionreporter, unit, severity, timestamp
Defect inspectedfn::lifecycle::record_poce_stepinspector, photos, arrival point, findings
Defect fixedfn::lifecycle::record_poce_stepcontractor, fix description, parts, completion photo
Defect signed offfn::lifecycle::finalize_poce_sessioninspector sign-off, handover certificate
Service charge disputedfn::lifecycle::start_poce_sessionunit, amount, invoice ref, dispute reason
Service charge resolvedfn::lifecycle::record_poce_stepresolution, adjustment, board approval
Warranty claim settledfn::lifecycle::finalize_poce_sessioncontractor fix, inspector sign-off, certificate

7. Worked Example — Defect / Snag Tracking

  1. Resident reports a water leak in unit A-1001 via WhatsApp intake.
  2. Claim created: cns://claim/type/real-estate/defect, bound to resource:unit_A-1001, PoCE session started.
  3. Property manager assigns inspector via panel eligibility (quorum: one-person for low severity).
  4. Inspector visits, records timestamped photo + GPS arrival point, logs defect findings.
  5. Contractor assigned via sourcing bus (qualified, nearest, certified), quote approved by property manager.
  6. Contractor fixes leak, uploads completion photo.
  7. Inspector re-visits, signs off on fix.
  8. Claim finalized with PoCE receipt: reporter → inspector → contractor → inspector sign-off chain.
  9. Escrow releases payment to contractor against verified proof (service charge finance desk).

Guard check: Inspector ≠ Contractor (SOD enforced). No payment without proof (escrow hold/release via fn::escrow::hold / fn::escrow::disburse).


8. What We Do Not Build

  • No land-registry replacement. Title remains with the land registry; Sovereign OS mirrors title references via integration_entity.
  • No dynamic property valuation. Unless expressible as solver-gateway capability + declarative lookups.
  • No synthetic "optimal" repair route or service-charge budget. Solver down → 502/503 fail closed.
  • No fake metrics (e.g., "98% defect resolution rate"). Live data or honest empty states.

9. Deployment

  1. Deploy strata: s206_claim_dependency_cascade, s210_claim_validation_registry, s214_claim_arbitration, s233_unified_claims, s282_processing_claim
  2. Seed CNS types: cns://claim/type/real-estate/*
  3. Seed lookups: guard policies, quorum bands, SLA windows, panel roles, intake maps in NATS KV
  4. Seed scenario packs: real estate defect, service charge, warranty packs
  5. Test: GET /v1/claims/processing/readiness — all probes must pass before LIVE