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

Feature Package PK-08 — Construction & Snagging (Handover)

Status: Package Specification
Domain: Construction / Handover / Quality
Maps to: Process 2 (Task Lists & Checklists), Process 8 (Asset Maintenance)
External integration: MinIO (evidence photos), OpenMAINT (contractor work orders)


1. What This Package Does

Gives the project team and snagging inspectors one auditable system for construction quality and handover — tracking defects/snags per unit, assigning contractors, recording evidence, and certifying handover — replacing photo logs on phones, email threads, and unsigned handover forms.

2. Features & Functionality

FeatureWhat it doesWho uses itWhat stands behind it
Defect / snag reportingInspector or resident logs a defect (unit or common area) with photo, severity, locationInspector, resident, project managercns://claim/type/real-estate/defect; photo hash in claim.evidence; MinIO
Snag list per unitAll defects for a unit grouped into a snag list; status tracked to closureProject manager, snagging inspectorMultiple claim:defect edges to one resource:unit
Contractor assignmentDefect assigned to responsible contractor (builder, plumber, electrician)Project managertruth_edge:assigned_to → truth_node:contractor
Evidence packBefore/after photos, measurements, certificates attached to each defectInspector, contractorMinIO; SHA-256 on claim.evidence
Handover gateUnit cannot be handed over until all snags cleared and signed offProject manager, legalCross-package gate (PK-01 sale handover)
Defect closureContractor marks complete; inspector verifies; expert sign-offContractor, inspectorfn::poce::record_step; SoD (inspector ≠ contractor)
Warranty trackingDefects within defect-liability period tracked; re-opened if recurringProject managerDefect claim traits (warranty_period, reopened); SLA

3. Workflow (Snag to Handover)

  1. Unit completed → snagging inspection scheduled
  2. Inspector logs defects with photos → defect claims bound to unit
  3. Defects assigned to contractors → work orders (OpenMAINT) created
  4. Contractors fix defects, upload completion photos
  5. Inspector verifies fixes; signs off (SoD: inspector ≠ contractor)
  6. All snags cleared → unit → READY_FOR_HANDOVER
  7. Handover released (PK-01); defect claims archived with warranty tracking
  8. PoCE receipt for the full snag-to-handover lifecycle

4. Guard Rails

  • No handover while any snag task is OPEN
  • No auto-close without expert sign-off (inspector ≠ contractor)
  • No defect without photo evidence (SHA-256)
  • No synthetic contractor IDs
  • OpenMAINT owns asset spec; Sovereign owns defect state and sign-off

5. Evidence & Audit

  • Defect claims, photo hashes, work-order refs, contractor records, inspector sign-offs, handover gate records, PoCE receipts