Logistics in Muthari OS closes the gap between the factory gate and the site gate for contractors who fabricate what they install. A delivery note is issued by the server for QC-passed zones only; if it is wrong it is superseded by a new note, never edited. Each shipped zone gets a QR code, minted once for life. The note rides a trip with a named driver and vehicle; the driver confirms and the note closes; site records receipt under the name on the signed proof of delivery. So ‘what left, on which truck, and who signed for it’ is three records written at the time, not a phone call to the driver.
Created, superseded and marked delivered by server calls; the note’s status has exactly one owner. Putting a zone that has not passed factory QC on a note is refused.
Every note is assigned to a trip with a driver and a vehicle, and trips carry their own status. The driver’s confirmation closes the linked delivery note, so the office sees the truck has arrived without asking.
Minted at delivery-note issue, one code per zone, resolved only inside your company. A scan opens the zone’s whole history and routes the person to the worklist their role owns — a scan never writes and never approves; a deliberate press does.
Receipt is refused unless the zone is Dispatched. It records the receiver’s name from the proof of delivery (deliberately, not the logged-in account), a reference and a note; it closes the note and notifies the material-inspection holders that there is something to inspect.
A wrong note is replaced by a new one and the old one stays on file, so the record always matches the paper the driver actually carried.
A received zone can be installed and inspected on Site; the zones that may ship come from Production. Muthari OS is built by contractors in the trade.