Hi Reelay 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. The envelope is a set of declared safety properties URML checks before motion. Reelay is interesting to URML because it builds efficient runtime monitors from temporal-logic specifications, header-only C++, which is the kind of thing that can actually run on a robot alongside the validated program.
Nothing here asks Reelay to change or maintain anything. This is a request for comment.
The division: URML rejects inadmissible intent before dispatch; a Reelay monitor enforces an envelope property at runtime. Two real questions. First, do URML envelope properties (bounds and timing conditions held over execution) map naturally onto Reelay's past-time MTL, or do some need future-time operators that change the deployment story? Second, what is the cleanest boundary for "URML declares the property and emits the signals, Reelay compiles and runs the monitor" on an embedded target?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0363-reelay-outreach.md
Thanks for Reelay; efficient header-only monitors are rarer than the need for them.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Hi Reelay 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. The envelope is a set of declared safety properties URML checks before motion. Reelay is interesting to URML because it builds efficient runtime monitors from temporal-logic specifications, header-only C++, which is the kind of thing that can actually run on a robot alongside the validated program.
Nothing here asks Reelay to change or maintain anything. This is a request for comment.
The division: URML rejects inadmissible intent before dispatch; a Reelay monitor enforces an envelope property at runtime. Two real questions. First, do URML envelope properties (bounds and timing conditions held over execution) map naturally onto Reelay's past-time MTL, or do some need future-time operators that change the deployment story? Second, what is the cleanest boundary for "URML declares the property and emits the signals, Reelay compiles and runs the monitor" on an embedded target?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0363-reelay-outreach.md
Thanks for Reelay; efficient header-only monitors are rarer than the need for them.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.