RFC: Open standard for robot-to-human light signaling — looking for technical feedback from ROS 2 developers

Hi everyone,

I’m working on an open standard called LSEP (Luminae Signal Expression Protocol) — a state machine specification for how robots communicate intent, awareness, and safety states to humans through light signals.

The problem it solves:

Most robotic platforms implement ad-hoc LED patterns with no shared semantics. Robot A blinks blue for “idle,” Robot B blinks blue for “navigating.” There’s no interoperability, and no way for a human in a shared workspace to learn one signal language that transfers across platforms.

LSEP defines a modular 9-state architecture: 6 Core states (IDLE, AWARENESS, INTENT, CARE, CRITICAL, THREAT) and 3 Extended states (MED_CONF, LOW_CONF, INTEGRITY) with deterministic mappings from sensor inputs like Time-to-Collision (TTC) to signal outputs. The full spec is open: https://lsep.org

Where ROS 2 comes in:

We’ve designed LSEP to run as an isolated safety node — it reads from your perception pipeline (TTC, proximity, sensor health) and publishes signal commands. It doesn’t touch your navigation stack. The architecture pattern uses lifecycle nodes to keep the signaling guardrail separate from autonomy logic.

What I’m looking for:

We’re running a free Beta program for 20 ROS 2 developers who want to stress-test the integration. No cost — your payment is brutal, unfiltered technical feedback and (optionally) a short write-up on how it fits into your stack.

The program covers:

- Translating TTC and proximity data to deterministic state machine outputs

- EU AI Act compliance layers (Art. 9 & 50) for high-risk physical AI transparency

- LSEP core & extended states: mechanics of the 9-state multimodal standard

- ROS 2 integration: isolating the LSEP safety node from your navigation stack

- Sensor fusion resilience: hysteresis and fallback patterns for sensor dropouts

Not looking for:

This isn’t a pitch. I’m not selling anything here. I’m looking for the people who actually build these systems to tell me where LSEP breaks, what’s missing, and what’s naive. The harshest feedback is the most useful.

Full spec: https://lsep.org

Beta registration: https://www.experiencedesigninstitute.ch

— Nemanja Galić

Déjà vu? https://discourse.openrobotics.org/t/lsep-open-protocol-for-standardized-robot-to-human-state-communication-light-sound-motion

1 Like