Live public status

HalNora One
development status.

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.

Status policy

Development progress is not a release promise.

“Active development,” “field validation” and “prototype” describe current work. General availability requires the appropriate security, device, integration, recovery and field-acceptance gates.

Last updatedOctober 12, 2026
Product status

Current work across HalNora One.

Development status is directional and may change as engineering, security, device, integration and field validation continue.

Active development

HalNora Dispatch

Courier/delivery, taxi, NEMT and field-service execution models; native Driver/Communications integration; Booking/Marketplace contracts; device, integration and release validation.

Open product →
Active staging / QA

HalNora Dispatch Entry

Preserve proven V20 workflows while adding merchant order controls, merchant-owned drivers, permission-controlled CSV imports, auditable ownership isolation and selected standalone V21 enhancements.

Open product →
Pilot / active development

HalNora Marketplace

Customer-live storefront operations, vendor/service-provider rollout, Marketplace-owned zones/pricing, supplier API/import review controls and Booking/Dispatch/POS/Inventory contracts.

Open product →
Development / field QA

HalNora POS

KDS/Expo, Inventory consume/reverse safeguards, operational close, first-tenant readiness and provider-neutral terminal integration.

Open product →
Active development

HalNora Booking

Provider QA, direct-URL RBAC acceptance, publication/live-email controls and broader authenticated modify/cancel workflows.

Open product →
Field validation

HalNora Communications

Driver/Dispatch integration, locked-screen hardware-key initiation, Bluetooth/audio routing and broader rugged-device validation.

Open product →
Active development

HalNora CRM

Three-proof account linking, signed short-lived authority, PostgreSQL rehearsal, authenticated cross-product testing and production-readiness hardening.

Open product →
Active development

HalNora Accounting

Durable receipt/idempotency storage, authenticated bank integrations, statutory accuracy, close/recovery controls and production financial E2E.

Open product →
QA validation

HalNora Inventory

Backup/restore proof, provider reconciliation, business release approval and controlled commercial enablement.

Open product →
Development QA

HalNora Payroll

Database-backed authenticated E2E, mandatory MFA, PostgreSQL identity safeguards, statutory calculation validation and later banking/CRA/Accounting integration.

Open product →
Early regulated prototype

HalNora Pharmacy

Persistent processing, database migration/concurrency validation, live pharmacy connectors, controlled Dispatch callbacks, privacy/compliance review and production authorization.

Open product →
Active development

HalNora Payments

Canadian Poynt Payment Bridge test path, provider-neutral payment contracts, terminal outcome/reconciliation flows and future Android Tap to Pay investigation.

Product status →
Early development

HalNora HR

Restricted runtime connection, secure workspace/membership bootstrap, verified employee self-service, authenticated two-business testing and later controlled HR→Payroll integration.

Product status →
The live status feed is temporarily unavailable. This page is showing the last published website snapshot.
Recent milestones

Public development milestones.

Only public-safe milestones appear here. Internal experiments, credentials, customer data and unapproved release claims are intentionally excluded.

Dispatch Entry

V20-first standalone entry track advances through staging QA

The V20-first rebuild has validated theme and merchant-ownership boundaries plus auditable merchant order controls. My Drivers is installed and QA-enabled; two-pool assignment and the standalone V21 Driver PWA path remain planned/disabled.

Details →
Marketplace

Configured storefront reaches customer-live pilot state

A configured Marketplace storefront is customer-live with 43 active listings, four delivery zones/rates, seven-day hours, PayPal webhook, Google Maps and V22 Dispatch connection. Supplier ingestion remains fail-closed with no supplier feeds.

Details →
Inventory

Isolated QA posting validates replay and duplicate safeguards

Inventory QA completed 21 synthetic postings with 36/36 tests, safe replay of concurrent requests, duplicate rejection, four serial movements and zero discrepancies. Commercial posting remains disabled.

Details →
Accounting

Financial-write safety advances in v1.79

Accounting reports 236/236 test files passing with command fingerprints, operation keys and fail-closed replay rules. Durable receipt storage remains a release gate and no live financial writes are enabled.

Details →
Pharmacy

Synthetic delivery and database-readiness safeguards advance

Synthetic review, reconciliation, delivery-event, callback/retry, POD and database-readiness safeguards progressed. Persistent processing, live callbacks, real dispensing and patient-data exchange remain disabled or unverified.

Details →
Booking

Self-service cancellation and credential lifecycle pass development checks

Cancellation propagated to the same V22 Work without duplication; credential issue/rotate/use/revoke and multi-workspace isolation also passed. Broader provider and direct-URL RBAC acceptance remain open.

Details →
CRM

Security linking safeguards advance with 146 passing tests

CRM reports 146 tests passing with TypeScript clean, plus stronger short-lived signed authority and replay/mismatch/expiry protections. Full PostgreSQL rehearsal and live cross-product identity acceptance remain open.

Details →
Payroll

Staged MFA protections advance in v16.2

Payroll reports 160/160 non-hook tests passing with TypeScript clean. Database-backed authenticated E2E, mandatory MFA and Canadian statutory validation remain open; live payroll and remittance flows stay disabled.

Details →
HR

Cross-business authorization work passes isolated tests

HR reports 35 unit-test files passing with TypeScript clean and isolated cross-business checks. RLS and restricted-runtime acceptance remain open, with invitations, private files and live Payroll sync disabled.

Details →
Communications

Native PTT validation passed key two-phone scenarios

Two-way PTT, locked-screen receive, lock/unlock persistence, Wi-Fi↔cellular recovery and physical PTT-key mapping passed in the current native test track.

Details →
Roadmap snapshot

Build. Validate. Recover. Expand deliberately.

Roadmap stages are centrally maintained and remain directional.

HALNORA ONE WORKSPACE FOUNDATION

Shared business context · catalogue · staff · permission-aware access

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.

INDEPENDENT DISPATCH TRACKS

Dispatch Entry (V20-first) · V21 field track · Phase 3C/MS1 · V22 commercial foundation

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.

PRODUCT DEVELOPMENT & VALIDATION

Dispatch · Dispatch Entry · Marketplace · POS · Booking · Communications · CRM · Accounting · Inventory · Payroll · Payments · HR

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.

EARLY REGULATED PROTOTYPE

HalNora Pharmacy

Pharmacy continues as a controlled privacy-first regulated prototype. Production authorization, live pharmacy-system connectors, persistent processing and regulatory acceptance remain intentionally gated.

SHARED CAPABILITIES & FUTURE VERTICALS

Hospitality & Event Operations · Fleet · Data & Migration · additional verticals

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.

Engineering context

Development publication is not general availability.

HalNora publishes selected development status so the roadmap is transparent without overstating commercial readiness.

01

Dispatch tracks stay separate: Dispatch Entry is the V20-first standalone entry product; V21 is an independent field/legacy reference; Phase 3C/MS1 is its own guarded acceptance track; V22 is the separate HalNora One multi-vertical commercial foundation.

02

Workspace links are deliberate: business switching and permission-aware access are functioning, but standalone products are not all connected to one shared login yet.

03

Payments stay processor-neutral: Canadian Poynt Payment Bridge availability is confirmed, but live provider testing and acceptance remain open.

04

Portability remains a requirement: current builds remain on Floot for now, while the architecture is designed to avoid permanent hosting lock-in and support future HalNora-controlled deployment.

Questions or investment

Talk with HalNora.

For investment opportunities, product questions or strategic partnerships, contact Roger.