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

Service Provider — Claims Player

Audience: Garages, clinics, contractors, repair shops, service businesses. Role: Service performer, evidence provider, payment recipient. Substrate: truth_node:person / truth_node:organization (provider), integration_entity (provider mirror), sourcing bus, escrow disbursement.


1. Role in Claims Processing

Service providers perform the work that resolves claims — garage repairs, medical treatment, contractor defect rectification. Providers are sourced through the sourcing bus (qualified, nearest, certified), perform work, upload evidence, and receive payment via escrow release against verified proof.

FunctionCanonical PrimitiveExample
Provider registrationtruth_node:organizationGarage, clinic, contractor business
Capability attestationAPF role + capabilitymotor_body_repair, medical_adjudication, construction_repair
Work evidenceclaim metadata + MinIOCompletion photo, parts used, labor hours
Payment receiptfn::escrow::disbursePayment released against verified proof

2. Capabilities & Attestations

CapabilityRequired ForAttestation Source
motor_body_repairGarage role (motor claims)Garage certification + licensing
glass_repairGarage role (auto glass)Glass repair certification
paint_workGarage role (auto body)Paint certification
service_renderedProvider role (medical claims)Clinical licence
dispensingProvider role (pharmacy claims)Pharmacy licence
clinical_documentationProvider role (medical claims)Medical records certification
defect_rectificationContractor role (construction)Contractor licence
construction_repairContractor role (construction)Construction certification

All capabilities require: approved affiliation + active status + attestation. Lease TTLs: one hour for operational roles.


3. Sourcing Eligibility — Provider

Providers are sourced through the sourcing bus (platform.criteria.v1.sourcing.requirement). The sourcing plane qualifies candidates against declared criteria (TGC) and solves the assignment (solver-gateway branch_and_bound 1.4.0).

CriterionDescription
QualificationProvider must hold required capability attestation
LocationNearest qualified provider to claim location
AvailabilityProvider must have capacity for the claim
CostSolver optimizes for least cost among qualified candidates
AttestationProvider must have active attestation for the capability

Unqualified providers are never shortlisted even if nearer or cheaper. Infeasibility returns a terminal fill_infeasible verdict — no fake match.


4. Evidence Requirements — Provider

Claim TypeProvider EvidenceFormat
Motor ClaimRepair completion photo, parts used, labor hours, warrantyMinIO + claim metadata
Home ClaimRepair completion, materials, contractor licenceMinIO + claim metadata
Medical ClaimService rendered, clinical notes (PHI-scrubbed), diagnosis codesMinIO (encrypted) + hash reference
Pharmacy ClaimDrug dispensed, quantity, prescriber, pharmacy NABPPharmacy system + claim metadata
ConstructionRectification evidence, contractor fix, inspector sign-offBuilding inspection + completion photo

Providers cannot approve their own close (separation of duties). Missing sorting or arrival checks are refused rather than guessed.


5. Payment Flow — Provider

  1. Provider assigned via sourcing bus (qualified, nearest, certified).
  2. Quote approved by claim approver (adjuster, property manager, etc.).
  3. Work performed — provider completes service, uploads evidence.
  4. Inspector verifies — completion evidence reviewed, sign-off recorded.
  5. Escrow holds payment — fn::escrow::hold against verified proof.
  6. Escrow releases — fn::escrow::disburse against inspector sign-off.
  7. Payment recorded — PoCE receipt sealed: provider → inspector → payment chain.

Guard check: Escrow releases only against verified proof. Provider cannot self-approve. No cash handling by playbooks — mobile-money or bank transfer where money moves.


6. Worked Example — Garage Motor Repair

  1. Motor claim filed — vehicle accident, photos, police report.
  2. Garage sourced via sourcing bus — three qualified garages offer, solver binds the pair covering the repair at least cost.
  3. Quote approved — adjuster approves garage quote within estimate band.
  4. Repair performed — garage fixes vehicle, uploads completion photo + parts invoice.
  5. Inspector verifies — inspector re-visits, signs off on repair quality.
  6. Payment released — escrow disburses to garage against verified proof.
  7. Claim finalized — PoCE receipt: broker → adjuster → garage → inspector → payment chain.

Guard check: Adjuster ≠ Garage. No payment without completion photo + arrival point + inspector sign-off.


7. What We Do Not Build

  • No provider-specific tables. All provider data maps to truth_node / integration_entity / sourcing candidates.
  • No pricing engine. Repair estimates are external; Sovereign OS mirrors estimate references.
  • No synthetic "optimal" provider. Solver down → fill_infeasible verdict; no fake match.