Plenty to FRET About: From Hazard Analysis to Formal Requirements for Robot-Assisted Dressing

Gunjari Chakraborty, Yasmin Rafiq, Hazel M. Taylor, Marie FarrellarXiv 2026 · DOI · arXiv

TL;DR

This paper explores the rigorous process of transforming 146 hazard-derived natural-language requirements for a robot-assisted dressing system into 117 unique formal specifications using NASA’s FRET tool. The authors demonstrate that formalization is far more than a translation exercise; it is a critical refinement process that exposes hidden ambiguities, necessitates the quantification of vague terms like "timely," and reveals complex structural relationships within human-robot teamwork.

What Problem Does This Paper Address?

Developing autonomous systems that interact closely with humans—such as a robot helping a person get dressed—is inherently safety-critical. To ensure these systems behave correctly, engineers use formal verification. However, there is a massive "specification bottleneck": requirements usually start as messy, ambiguous natural language (NL) that analysis tools cannot understand.

In the context of Human-Robot Teamwork (HRT), this is even harder. Requirements must balance high-level teamwork concerns (like "who is in control?") with low-level safety constraints. This paper investigates how to bridge the gap between a high-level HRT taxonomy and the precise temporal logic needed for formal verification, using a Robot-Assisted Dressing (RAD) system as a case study.

Figure 1: Workflow for the Robot-Assisted Dressing (RAD) use case, including several hazards [28].

Methods

The researchers followed an iterative methodology to formalize 146 requirements previously derived from a hazard analysis of the RAD system.

  1. Classification: Requirements were mapped to a six-category HRT taxonomy (e.g., Information Sharing, Safety and Risk Mitigation).
  2. Formalization with FRET: They used NASA’s Formal Requirements Elicitation Tool (FRET). FRET allows users to write requirements in FRETISH, a structured natural language that looks like English but has a strict underlying mathematical semantics. FRET then automatically generates Linear-Time Temporal Logic (LTL) or Probabilistic Computation Tree Logic (PCTL*) formulas.
  3. Expert Refinement: The team spent roughly 10 hours consulting with domain experts to resolve ambiguities discovered during formalization.
  4. Analysis: They performed realizability checking using the Kind2 tool to ensure the requirements weren't contradictory (i.e., that it is actually possible to build a system that satisfies all of them simultaneously).
Figure 2: Hierarchy of categories from the Human-Robot Teamwork (HRT) requirements taxonomy in [23]. The blue boxes represent high level categories and the orange boxes denote low level categories.

Datasets

The primary "dataset" is a corpus of 146 natural-language requirements derived from a hazard analysis of the RAD system. These requirements cover various stages of dressing, from garment identification to arm insertion. The resulting formalized dataset consists of 117 unique FRETISH requirements, which the authors have made available in a public GitHub repository (cradlerobotics/RAD).

Key Insights and Ideas

  • Formalization as a "Truth Serum": The process forced the team to define vague qualitative terms. For example, "timely" was quantified as "within 30 seconds," and "high accuracy" was formalized as a probability threshold (e.g., $\ge 0.9$).
  • Decomposition and Consolidation: The mapping from NL to formal logic is rarely 1-to-1. A single NL requirement often contained multiple distinct obligations (decomposition), while multiple hazards sometimes led to the exact same formal safety property (consolidation).
  • Temporal Dominance: A significant majority (70.1%) of the unique requirements relied on immediately or before constraints. This highlights that HRT in physical tasks is primarily about reactive safety (stop immediately if a human moves) and strict ordering (don't confirm a garment until it's validated).
  • Complementary Views: The HRT taxonomy and FRETISH serve different purposes. The taxonomy captures the intent or teamwork concern (the "why"), while FRETISH captures the behavioral obligation (the "what").
Table 1: Selected natural-language requirements with accompanying FRETISH

Key Results

  • Requirement Transformation: The 146 source requirements were distilled into 117 unique formal properties. The largest category was "Safety and Risk Mitigation" (42 unique requirements).
  • Timing Distribution: The study found that immediately (44 requirements) and before (38 requirements) were the most common temporal constructs, differing from previous FRET studies in other domains where eventually and always were more prevalent.
  • Conflict Detection: Realizability analysis successfully identified logical conflicts. For instance, one requirement demanded an immediate response to a command, while others required multiple modalities (voice and gesture) to be confirmed first. This highlighted a need for clearer system initiation assumptions.
Table 2: Formalisation coverage across the high-level HRT taxonomy categories

Limitations and Future Work

  • Case Study Specificity: The findings are based on a single RAD case study. The authors acknowledge that these patterns might not generalize to all HRT applications.
  • Tooling Limitations: FRET currently lacks a way to "call" or reference one requirement within another, leading to some repetition. The authors suggest exploring the "Mu-FRET" extension to handle requirement refactoring.
  • Variable Relationships: The tool doesn't yet support defining semantic relationships between variables (e.g., that a "correct" variable must also be "valid").
  • Future Directions: The team plans to apply this approach to other HRT scenarios and investigate how these formal properties can directly support automated verification and validation (V&V) activities.

Summary updated

Abstract

Understanding requirements for systems involving humans and robots is essential for providing robust evidence that such systems behave correctly. Requirements formalisation approaches such as the Formal Requirements Elicitation Tool (FRET) can support the transition from unstructured natural language to formal representations suitable for verification. In this paper, we formalise 146 hazard-derived natural-language requirements for a Robot-Assisted Dressing (RAD) case study, previously classified using a taxonomy of Human-Robot Teamwork (HRT) requirements. Through an iterative process involving domain-expert clarification, these were represented by 117 unique FRETISH requirements. Formalisation exposed ambiguities, temporal and probabilistic assumptions, and cases where source requirements needed to be decomposed or could be consolidated because they expressed the same formal behaviour. Temporal analysis showed that 70.1% of the unique FRETISH requirements use either immediate-response or ordering constraints (immediately or before), while formalisation also exposed relationships between requirements across HRT taxonomy categories. We further analyse the formal semantics and realisability of the resulting requirements. The results show that HRT classification and formalisation provide complementary views: the taxonomy captures the teamwork concern represented by a requirement, while FRETISH makes the required behaviour explicit. We report practical lessons and limitations of applying FRET to HRT requirements and identify directions for further work.
BibTeX
@misc{chakraborty2026plenty,
  author = {Gunjari Chakraborty and Yasmin Rafiq and Hazel M. Taylor and Marie Farrell},
  title = {{Plenty to FRET About: From Hazard Analysis to Formal Requirements for Robot-Assisted Dressing}},
  year = {2026},
  eprint = {2611.22399},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2611.22399},
}
Figure