What we're building first, and what waits

ZQX is built by one person, and every build decision has to respect that. Distributed services, event streaming infrastructure, and a separate analytics store all wait until a specific, measured problem justifies them; the platform starts as a modular monolith and stays that way until it genuinely cannot.

The build order follows the same operator path a real depot or transport desk would walk: locale and app shell, tenant and access setup, equipment, the business network of clients, carriers, facilities, and contacts, then booking, job, and transport leg execution. Status, readiness, and proof sit on top of that foundation rather than ahead of it, because a status is only trustworthy once there is real evidence underneath it.

Multi-tenancy, row-level tenant isolation, an append-only audit trail, and scoped external visibility are treated as foundational from the first schema, not features to retrofit once real tenants are on the platform. The same discipline applies to every consequential operational, compliance, or billing decision: it comes from a deterministic rule over verified data, with a human always able to review and override it.

Later-stage work, cross-data intelligence, billing automation, saved views, native mobile, and OCR-assisted document intake, is sequenced deliberately after the operational core, so it is built on data that is already trustworthy rather than on assumptions the platform has not earned yet.