Hi Furhat maintainers,
URML (urml.dev) is a small, Apache-2.0 language for robot intent: an intent becomes a typed primitive, validated against the robot's declared capabilities and a safety envelope, then dispatched. Furhat is a social conversational robot, and URML is the validated-intent layer for physical robot action -- so this is a narrow, honest note about one possible seam.
Nothing here asks the project to adopt, host, or maintain anything. This is a request for comment.
The seam: a Furhat skill owns the social interaction. If a skill ever triggers a physical action on a connected robot (a mobile base, an arm, a device), URML is the typed, validated representation of that action -- checked against the robot's capabilities and a safety envelope before it runs. Furhat stays the conversational brain; URML is the gate on the physical limb. If Furhat skills never drive an external physical robot, then the seam is empty and this is just a friendly hello -- which is why the first question is genuine.
Two real questions: (1) do Furhat skills ever drive an external physical robot as part of an interaction? (2) If so, is a typed, validated intent layer between a skill and that physical robot useful?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0552-furhat-example-skills-outreach.md
Thanks for the Furhat skills; social robotics is a different world from actuation, and I am genuinely curious whether the two ever touch in your deployments.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see https://github.com/URML-MARS/URML/blob/main/VIBE.md). Human-only correspondence available on request.
Hi Furhat maintainers,
URML (urml.dev) is a small, Apache-2.0 language for robot intent: an intent becomes a typed primitive, validated against the robot's declared capabilities and a safety envelope, then dispatched. Furhat is a social conversational robot, and URML is the validated-intent layer for physical robot action -- so this is a narrow, honest note about one possible seam.
Nothing here asks the project to adopt, host, or maintain anything. This is a request for comment.
The seam: a Furhat skill owns the social interaction. If a skill ever triggers a physical action on a connected robot (a mobile base, an arm, a device), URML is the typed, validated representation of that action -- checked against the robot's capabilities and a safety envelope before it runs. Furhat stays the conversational brain; URML is the gate on the physical limb. If Furhat skills never drive an external physical robot, then the seam is empty and this is just a friendly hello -- which is why the first question is genuine.
Two real questions: (1) do Furhat skills ever drive an external physical robot as part of an interaction? (2) If so, is a typed, validated intent layer between a skill and that physical robot useful?
Full write-up: https://github.com/URML-MARS/URML/blob/main/docs/rfcs/0552-furhat-example-skills-outreach.md
Thanks for the Furhat skills; social robotics is a different world from actuation, and I am genuinely curious whether the two ever touch in your deployments.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see https://github.com/URML-MARS/URML/blob/main/VIBE.md). Human-only correspondence available on request.