Roadmap

OpenRoIS is built in phases. Each phase delivers a coherent capability with explicit exit criteria. Until version 1.0, releases are alpha, with an unstable API.

Overview

Phase	Theme	Status
0	Paradigm-neutral interface types	Done
1	Engine and sub HRI Engine proof of concept	Done
2	Adapter framework and reference components	Done
3	Client SDKs and first end-to-end demonstration	In Progress
4	Recursive core in Python	Done
5	Hardening the core	In Progress
6	Gateway process	Done
7	Adapter process	Planned
8	Open reference platform and mixed paradigms	In Progress
9	Authentication, security, and media	In Progress
10	Full component library (v1.0)	Planned
11	Component registry and Hub	After 1.0

Phase 3 continues alongside phases 5 and 6. Phases 8 and 9 can proceed in parallel once the gateway and adapter processes exist.

Phase Details

Phase 0: Paradigm-Neutral Interface Types

RoIS types authored as Python models, exported to JSON Schema, and generated into TypeScript and C#, with tests against the normative RoIS files. Definition of the five-method Component Contract.

Phase 1: Engine and Sub HRI Engine Proof of Concept

A TypeScript engine that routes RoIS calls to sub HRI Engines over WebSocket, aggregates their profiles, tracks reservations, and broadcasts profile changes.

Phase 2: Adapter Framework and Reference Components

The decorator-based component framework, component-owned backend connections, and reference Navigation and System Information components for the Preferred Robotics Kachaka with gRPC and ROS 2 backends.

Phase 3: Client SDKs and First End-to-End Demonstration

• Done: the TypeScript SDK, the profile-driven web client, the mock engine, and an end-to-end demonstration of a web application controlling a physical robot through the gateway and an adapter.
• Done: the C# client SDK for Unity (RoISClient, callbacks on the main thread).
• Exit: tagged release v0.1.0.

Phase 4: Recursive Core in Python

The openrois-core package: the recursive Engine, the component registry and the child engine proxy implementing the typed Component Contract, the WebSocket server and client, every Command, Query, and Event operation except streaming, command completion and error notifications, and a regression test suite with a gateway plus adapter round trip. The TypeScript proof of concept is retired.

Phase 5: Hardening the Core

• Done: control-plane latency benchmarks on loopback with the mock adapter; LAN and Kachaka numbers are still to be measured.
• Done: a GET /health liveness endpoint on the gateway port.
• Planned: graceful shutdown, reconnection behavior, and loading component packages from a local path or a Git URL.

Phase 6: Gateway Process

• Done: the openrois-gateway process and its container image, composed from Engine and WsServer, with command-line configuration, logging, signal handling, and docker compose up.
• Done: a YAML configuration file (--config, OPENROIS_GATEWAY_CONFIG) below the command line and the environment in precedence, and GET /health as the container's health check.

Phase 7: Adapter Process

A standalone adapter process composed from Engine, WsClient, and a backend bridge, configured by the adapter profile.

Phase 8: Open Reference Platform and Mixed Paradigms

• Done: the mixed-paradigm demonstration, examples/mixed-paradigm: a simulated robot and a text-based virtual agent behind one gateway, driven by one application with identical calls. See deployment topologies.
• In progress: a reference platform based on the open-source Pollen Robotics Reachy Mini, shipped with OpenRoIS so anyone can try the full stack on affordable hardware. The adapter, a simulated backend, and a one-command bring-up pass the conformance suite in simulation; verification on a robot is pending.
• Planned: the demonstration repeated with that robot and a rendered avatar. Completing this phase starts the transfer of OpenRoIS to a neutral open-source foundation.

Phase 9: Authentication, Security, and Media

• Done: JWT authentication at the WebSocket upgrade, role-based authorization per RoIS operation with scopes, and TLS at the gateway.
• Done: the Streaming Interface control plane: rois.stream.* operations routed to streaming components, stream status events routed back to the application that connected the stream, and stream methods in the TypeScript and C# SDKs.
• Planned: WebRTC media on the data plane, with the transport descriptor exchanged through connect_stream results, and DDS Security for ROS 2 based adapters. See security and transports and media.

Phase 10: Full Component Library

All 17 basic RoIS HRI Components, for physical robots and virtual avatars, and packages published to PyPI, npm, NuGet, and the Unity Package Manager. First stable release with semantic versioning guarantees: v1.0.

Phase 11: Component Registry and Hub

A registry of community components and adapters for additional platforms, and a Hub web application that visualizes connected adapters, components, and their status. This phase is gated on adoption and follows version 1.0.

Versioning

• 0.x releases are pre-releases. Breaking changes may happen without notice.
• 1.0 is the first release with semantic versioning guarantees.

Contributing to the Roadmap

Many items above can be picked up in parallel, and reference components for new robots are the natural entry point. See contributing, or open an issue to propose a change to the roadmap.