Current public-safe development status, focus areas and milestones across the HalNora One ecosystem. This page is fed by centralized status files so changing build information can be published without rebuilding the entire website.
A product may be published for development, complete for an approved standalone scope, in field validation, paused, or still gated. General availability requires that product’s applicable security, recovery, device/provider, business-accuracy and accountable release approvals.
Development status is directional and may change as engineering, security, device, integration and field validation continue.
Close the remaining native/mobile, PTT, payment-provider, tenant-isolation and clean-release gates while preserving the accepted core Dispatch, Marketplace/Booking, offline, POD, email and PWA workflows.
Open product →Preserve the staged V20-first work and its merchant/driver/import design while the current V20 freeze remains in force; no further V20-dependent development or release work is implied.
Open product →Finish real Driver mobile/PWA human acceptance, historical QA-order disposition and final security/release review while preserving Marketplace-owned pricing and product/service-provider boundaries.
Open product →Complete Poynt/N950 payment-provider acceptance, physical peripheral/KDS validation, remaining failure/recovery checks and final human release sign-off.
Open product →Preserve the completed standalone product; reopen only for approved optional capabilities such as permanent Marketplace mapping, customer email, shared identity or material scope changes.
Open product →Stabilize the V22 Dispatch↔Driver direct-radio connection, then finish network-handoff/native-package/locked-screen acceptance within the approved scope; Bluetooth and broader rugged-device work remain separate.
Open product →Finish independent recovery/restore, authenticated two-business security, database-role/RLS decisions, email/MFA and human operational acceptance without expanding the approved CRM scope.
Open product →Complete independently controlled financial concurrency/recovery, restricted database-role, bank/provider, statutory and professional acceptance before any real posting or filing is enabled.
Open product →Finish independent backup/restore, authenticated tenant/security, integration/reconciliation and release approval while keeping irreversible commercial stock posting disabled by default.
Open product →Close authenticated browser/MFA, statutory Canadian calculation, restricted database, backup/restore, banking/remittance and Accounting integration gates before any real payroll use.
Open product →Finish the original approved staff/driver/POD/security/POS acceptance gaps only; no new scope. Private POD storage/recovery, real device workflows, official pharmacy-system/vendor conformance and regulated review remain mandatory.
Open product →Move from simulated Poynt/terminal readiness into an approved merchant/device sandbox and verified payment/reconciliation flow without requiring customers to abandon compatible existing processor relationships.
Product status →Complete real tenant isolation with restricted database credentials, ordinary-user workflow acceptance, recovery and final security/release evidence while keeping live Payroll transmission disabled.
Product status →Only public-safe milestones appear here. Internal experiments, credentials, customer data and unapproved release claims are intentionally excluded.
Current release-gate data records Passed status for active integration, Core Dispatch workflow, HalNora email domain, map provider, offline/reconnect, POD device, PWA install/update, authenticated realtime and settlement reconciliation. Native packages/background GPS, native push, PTT, payment provider, tenant isolation and clean release/rollback remain open; production release is not approved.
The original Pharmacy project reports all 167 current spec files passing with TypeScript clean. It remains unpublished and synthetic-only; private POD storage/recovery, real device/role acceptance, official vendor conformance and regulated release approval remain open.
The owner approved Booking complete under the eight-point completion standard for its current standalone scope. Optional permanent Marketplace mapping, customer email and shared HalNora identity remain conditional future capabilities.
A synthetic Taidelish order passed Marketplace cart/quote and PayPal Sandbox through merchant preparation, signed Flex fulfillment, delivery callbacks and final completion. Separate fulfillment-cancellation response-loss/replay recovery also passed. Real Driver mobile/PWA acceptance and final release approval remain open.
HR is now focused on tenant isolation, ordinary-user acceptance, recovery and final release evidence rather than new features. The main project remains unpublished and live Payroll transmission stays disabled.
The approved CRM scope is being finished through security, recovery, PostgreSQL and human acceptance gates rather than feature expansion. The main project remains unpublished and production approval remains false.
The POS completion audit records real-user cash Sale/receipt/till/Return/Void/closeout workflows, authenticated two-tenant role isolation and a clean-schema PostgreSQL rehearsal. Payment-device/provider, physical hardware and final human release gates remain open.
Earlier V20-first staging work is retained as a separate investor/commercial track, but V20-related development is currently frozen. No further Entry Dispatch development or release claim is implied while that freeze remains in force.
Roadmap stages are centrally maintained and remain directional.
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.
HalNora publishes selected development status so the roadmap is transparent without overstating commercial readiness.