Development Plans
Products
Section titled “Products”- Spiral — a dynamic scheduling optimisation engine.
- Travel Calculator — an optional Spiral extension integrating the OSRM routing engine, with support for other routing solutions through Spiral’s open interface.
- Helix — Spiral Workforce Management: a web-hosted field workforce management solution for SMEs and enterprises, cloud or on-premises, with modules for field workers, deployment control and order management.
Versions
Section titled “Versions”| Application | Version | Name | State | Release date | Supported |
|---|---|---|---|---|---|
| Spiral | 1.0 | Basic Scheduling | Released | 01/08/2022 | No |
| Travel Calculator | 1.1 | Embedded OSRM | Released | 05/03/2025 | Yes |
| Spiral | 1.8 | Constraints | Released | 27/03/2025 | No |
| Spiral | 2.0 | Input Interpretation | Released | 02/09/2025 | No |
| Spiral | 2.1 | Offer | Released | 01/12/2025 | No |
| Spiral | 2.2 | Predicted Income | Released | 01/03/2026 | No |
| Spiral | 2.3 | Declarative | Released | 01/06/2026 | Yes |
| Helix | 0.0.1 – 0.0.2 | Dispatch and Applications | Released | 28/07/2026 | No |
| Spiral | 2.4 | Surge 2 | Released | 01/08/2026 | Yes |
| Helix | 0.0.3 – 0.0.4 | Supported Core | Released | 20/08/2026 | No |
| Helix | 0.0.5 – 0.0.6 | Logistics Hubs and Roster States | Released | 26/08/2026 | No |
| Helix | 0.0.7 – 0.0.8 | Standby Callout and Notifications | Released | 28/08/2026 | No |
| Helix | 0.0.9 | Actions Taxonomy | Released | 01/09/2026 | Yes |
| Helix | 0.0.10 | Audit and Archiving | Test | 07/09/2026 | — |
| Helix | 0.0.11 | SME Demo | Design | 14/09/2026 | — |
| Spiral | 2.5 | Logistics Hubs | Test | 01/10/2026 | — |
| Helix | 0.1 | Prototype | Test | 01/10/2026 | — |
| Spiral | 2.6 | Assets | Design | 01/01/2027 | — |
| Helix | 0.2 | Assets | Design | 01/01/2027 | — |
Helix milestones
Section titled “Helix milestones”Helix reaches its 0.1 Prototype milestone through the 0.0.x core series. Each milestone below names
the releases that built it.
- 0.0.1 – 0.0.2 · Dispatch and Applications. The surface itself: the dispatch screen, and the applications beside it — the Contact Centre, the Engineer app, Administration and Mission Control. Also the actions engine, surge zones, and multi-node clustering.
- 0.0.3 – 0.0.4 · Supported Core. The first officially released core. Its headline was delivery: the plan now arrives as a single bulk snapshot rather than thousands of per-event deltas, taking a 10,000-job stress test from around two and three-quarter minutes to sixteen seconds. Version pinning and bundle-core provenance arrived with it, so a node can always say which core it runs.
- 0.0.5 – 0.0.6 · Logistics Hubs and Roster States. The hub entity, matching Spiral’s staging-point work. Rosters gained off-duty shift states, so a resource’s status through its shift is derived rather than asserted, and scenario and live timing moved onto one shared event queue.
- 0.0.7 – 0.0.8 · Standby Callout and Notifications. The standby callout end to end — called, offered, accepted or refused, stood down on timeout — and the notification toolkit underneath it: an outbound queue with retry, pluggable channels, and inbound replies that close the loop.
- 0.0.9 · Actions Taxonomy. A systematic pass over what the operator is asked to do and when — processes composed of steps and actions — alongside eternal rosters and a reconciled location model.
- 0.0.10 · Audit and Archiving (in progress) — what is recorded and for how long, where it is kept once it leaves the live system, and how a node that has been running for years is kept to the work that still matters.
- 0.0.11 · SME Demo (planning) — self-service evaluation. Set your own company up, see Helix running against it rather than against someone else’s sector, and from there take up a hosted offer of up to 100 mobile units on a customised domain for your sector. It extends two things that already exist: the self-config wizard that builds a scenario to order, and the per-visitor demo sandbox.
- 0.2 · Assets (design) — the Helix side of asset optimisation, pairing with Spiral 2.6.
How the two products line up
Section titled “How the two products line up”There is no declared minimum Spiral version. Each Helix release carries its own Spiral engine, baked into the image, so a Helix version is the pin — and a running node reports the engine it actually found rather than one it was promised. Spiral 2.4.0a shipped in the 0.0.3 line, 2.5.0a in 0.0.5, and 2.5.0c in 0.0.8.
Versioning
Section titled “Versioning”Versions follow an x.y.z scheme:
- Major (x) — new releases that require host-interface updates.
- Minor (y) — development streams that may extend the API while remaining backward compatible.
- Increment (z) — official releases; only these receive support.