HalNora One is the stable ecosystem umbrella while product roadmaps remain independent. Progress is organized around clear authority, platform maturity, security, recoverability and field acceptance.
Development progress is described honestly; general availability waits for the appropriate product, device, integration, security and recovery gates.
The HalNora One workspace remains the shared business/product-navigation foundation while standalone products retain their own identity, tenant and release authority until explicit contracts are accepted.
V22 is the active HalNora One multi-vertical commercial Dispatch candidate. The V20-first Dispatch Entry track is preserved but paused under the V20 freeze. V21 and Phase 3C/MS1 remain independent operational/reference or acceptance tracks rather than one migration chain.
Booking was owner-approved complete on October 18 under the eight-point standard for its current standalone scope. Optional permanent Marketplace mapping, customer email and shared HalNora identity remain future/conditional capabilities.
These products are at different engineering/acceptance stages. Published development apps and passing automated suites are not equivalent to commercial release; each product keeps its own security, device, recovery, provider, business-accuracy and human-approval gates.
Pharmacy remains an unpublished synthetic prototype in completion mode. The original scope is frozen while staff/driver/POD/security/POS acceptance, private evidence recovery, vendor conformance and regulated approval are completed.
Hospitality/Event Operations and other verticals remain planned direction. Shared capabilities can be reused only after their underlying products and contracts reach the required acceptance level.
Different products have different blockers, but the ecosystem uses common release discipline.
These themes guide architecture and product boundaries but do not imply immediate implementation or general availability.
Coordinate front-of-house commerce, security, stage/production, maintenance, housekeeping, parking/transportation, medical/first aid, concessions/vendors and supervisors with staff/resource presence, tasks, incidents, Communications/PTT, alerts and permission-scoped VMS integrations.
Explore the planned workflow →Vehicle assignment, maintenance, registration reminders, odometer/fuel/expense history and configurable inspections.
Use route and field state to produce useful ETA, tracking and automatic alerts across Courier, Taxi, Medical and Field Service.
Model skills, equipment and requirements as a foundation for generalized auto-dispatch and advanced scheduling.
Barcode/QR workflows, bulk scanning, scan-to-assign, vehicle loading, run sheets and chain-of-custody support.
Extend secure dispatcher, merchant and worker access without duplicating the authoritative operational model across separate systems.