Architecture Layer: Sugarcoat Roadmap

Q1 2026 (Happening now): UI Improvement, Advanced Eventing & Telemetry

  • Professional Enterprise UI: Improving the auto-generated layouts to an enterprise-grade management console with customizable operator views. This requirement has emerged from the field. This includes assigning tasks, monitoring task progress, richer map view (with path, way points etc.) and an easier customization of frontend.

  • Global Robot State: Creating a centralized, extensible state that can track robot health, internal and environment variables. This will extend the current health status and add a multi-tier state that the robot can react to and even reason over, based on the adaptivity defined in the recipe. This state will be extended by the derivative packages and plugins.

  • Composite Event Creation: Introducing logic for “Composite Events” (e.g., Triggering an action only if Battery < 20% AND Current_Task == Idle). A unified global state makes these events plausible and very powerful.

  • Priority-Based Event Handling: Implementing a prioritized event queue to ensure safety-critical actions preempt high-level ones.

  • Telemetry: Adding component level telemetry to create track task specific recordings, specifically for components that produce physical actuation. This will allow for post-facto analysis (through visualization tools) and creating datasets from real world deployments.

Q2 2026 & Q3 2026: Core Migration & Visualization Tools

  • Advanced Goal Scheduling: A constraint-based scheduler for managing complex missions with temporal dependencies.

  • C++ Core Migration: Migrating the internal Sugarcoat event-orchestration layer in C++, reducing internal latency and enabling higher control frequencies.

  • Event & Action Visualizer (Studio): Developing a visual tool for developers to map event-to-action flows and users to monitor the real-time “Nervous System” of the robot. The monitoring part would enrich the dynamic web based UI.

Q4 2026 and Onwards: New Middleware Support

  • Native ROSZ Support: Integrating ROSZ (Zenoh based ROS), backend as a first-class middleware alongside rclcpp (ROS2) to enable high-performance, low-bandwidth communication. ROSZ is targetted at ultra-lightweight and low latency ROS like implementation. It is currently experimental.