ZQX product direction

Container status information travels by phone call and email across most operations today, with no shared record either side can point back to when something goes wrong. ZQX exists to replace that with one answer: Ready, Not Ready, Blocked, or Conditionally Ready, computed from recorded evidence and open holds rather than guessed or asserted over the phone.

The distinguishing idea is not the four statuses themselves; container logistics has always had some version of ready or not ready. It is that every status ZQX shows is derived deterministically from source data a person can inspect, and every human override is recorded: who made it, when, and why. A status that cannot be explained is not useful, no matter how confident it sounds.

That principle shapes the build order more than any feature list does. Equipment, bookings, jobs, proof, and holds all come before dashboards and automation, because the status only means something once there is real evidence underneath it. We would rather ship a smaller product that is honest about what it knows than a larger one that fills gaps with assumptions.

ZQX is built by one person, for real depot, transport, and forwarding operations, so scope stays deliberately proportionate: a modular monolith, one identity model, one tenant model, one audit trail, extended as real operational need justifies it rather than ahead of it.