Domain Model

Core Entity: Moked (Work Order)

The Moked (מוקד) is the central business object. One moked represents a single repair scope on a vehicle — for example, "front bumper damage" or "left side dent."

A vehicle can have multiple mokeds. ALL mokeds must complete before the vehicle can be delivered back to the customer.

Entity Relationships

Vehicle (identified by plate number)
  └── 1:N → Moked (work order per damage area)
               ├── 1:N → SubItem (part, job, hours, inspection, external)
               ├── 1:N → FilesCollection → FileData (photos, documents)
               └── 1:N → MondayUpdate (activity log)

SubItem Categories

Each moked contains subitems categorized as:

Category	Hebrew	Purpose
Part	חלק	Physical component to replace/repair
Job	עבודה	Labor/work task
Appraiser Hour	שעת שמאי	Appraiser time allocation
Inspection	בדיקה	Inspection checklist item
External Job	עבודה חוץ	Work done by external vendor

Key Business Rules

One vehicle, multiple mokeds: A vehicle with front + rear damage = 2 separate mokeds
All-or-nothing delivery: Car delivery requires ALL mokeds to be completed ("הסתיים")
SubItem independence: Each subitem tracks its own appraisal status, work status, and purchase status independently
Monday.com is the source of truth: Mokeds are items on Monday.com boards, subitems are Monday.com subitems

15 March 2026