Hi MoonLight maintainers,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: it validates a request statically against a capability manifest and a safety envelope, then dispatches. Some of the most important envelope properties are inherently spatial and temporal at once: a geofence held over time, a minimum separation distance maintained across a fleet of robots. That is exactly what STREL and MoonLight are built to monitor, which is why I am writing.
Nothing here asks MoonLight to change or maintain anything. This is a request for comment.
The division: URML declares the spatial-and-temporal envelope and validates intent before dispatch; a MoonLight monitor enforces the property at runtime. Two real questions. First, do URML envelope properties (a geofence, an occupancy region, a cross-robot separation) map onto STREL's reach and escape operators, or are some shapes hard to express? Second, for the multi-robot case (URML has a fleet deconfliction notion built on operational volumes), what spatial-graph and signal interface would a MoonLight monitor expect so the separation property could be checked over a live fleet?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0371-moonlight-outreach.md
Thanks for MoonLight; spatio-temporal monitoring is underserved and you are one of the few clean open tools for it.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Hi MoonLight maintainers,
URML (urml.dev) is a small, Apache-2.0 language for describing robot intent: it validates a request statically against a capability manifest and a safety envelope, then dispatches. Some of the most important envelope properties are inherently spatial and temporal at once: a geofence held over time, a minimum separation distance maintained across a fleet of robots. That is exactly what STREL and MoonLight are built to monitor, which is why I am writing.
Nothing here asks MoonLight to change or maintain anything. This is a request for comment.
The division: URML declares the spatial-and-temporal envelope and validates intent before dispatch; a MoonLight monitor enforces the property at runtime. Two real questions. First, do URML envelope properties (a geofence, an occupancy region, a cross-robot separation) map onto STREL's reach and escape operators, or are some shapes hard to express? Second, for the multi-robot case (URML has a fleet deconfliction notion built on operational volumes), what spatial-graph and signal interface would a MoonLight monitor expect so the separation property could be checked over a live fleet?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0371-moonlight-outreach.md
Thanks for MoonLight; spatio-temporal monitoring is underserved and you are one of the few clean open tools for it.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.