Hi all,
I’m looking for architectural experience around a situation in which a ROS 2 system remains technically healthy, but an external operating condition changes while the robot is already performing a task.
ROS 2 already provides important mechanisms for component lifecycle management, supervision and recovery. Nav2 adds planning, control, recovery behaviour and local collision-related mechanisms.
My question is adjacent to those capabilities, rather than a proposal to replace them.
Consider a mobile robot navigating in a shared facility.
Localization is valid. The planner and controller are operating normally. There is no immediate collision hazard and no component failure.
While the task is underway, however, an external operating condition changes. For example, an area that was previously available for the operation is temporarily no longer available.
Where should that kind of changing context be represented and evaluated in a real ROS 2 architecture?
Possible locations might include:
- the task or mission layer;
- a separate supervisory component;
- a fleet or facility-level service;
- or a combination of local and external components.
I would particularly value practical experience around four questions:
-
Which layer should own and update this kind of operating context?
-
How should the system behave if the external source of that context becomes unavailable or outdated?
-
How can higher-level operational logic be introduced without weakening existing local safety, recovery or lifecycle behaviour?
-
In a multi-robot environment, which parts of the operating context should belong to each robot and which should be shared?
I have read the recent discussions here around runtime accountability and runtime trust or authorization. My question is deliberately narrower: the technical stack is functioning as designed, but the conditions surrounding the operation have changed.
At Sentryn, we use “runtime governability” as a public research term for this broader class of questions. We are not announcing a ROS package or claiming a completed ROS 2 integration.
I am mainly interested in existing architectural patterns, operational experience, counterexamples and relevant prior work.
Public research-level context:
Critical feedback is very welcome, particularly from teams operating ROS 2 robots outside controlled laboratory environments.