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 provides a central product catalogue, shared business/staff context and business switching while product identity connections are enabled deliberately rather than assumed.
These four Dispatch efforts are intentionally independent. Dispatch Entry preserves proven V20 workflows with selected standalone V21 enhancements; V21 remains a separate field/legacy operational reference; Phase 3C/MS1 is its own guarded acceptance track; V22 is the separate HalNora One multi-vertical commercial foundation.
Twelve public development/validation tracks are moving in parallel across product and Dispatch-entry work. Progress does not equal general availability, and each track must pass its own security, device, integration, recovery and acceptance gates.
Pharmacy continues as a controlled privacy-first regulated prototype. Production authorization, live pharmacy-system connectors, persistent processing and regulatory acceptance remain intentionally gated.
Hospitality/Event Operations and other verticals remain planned direction. Shared capabilities continue to mature beneath the product family without turning every capability into a standalone product.
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.