| {"id": "rs_000096", "instruction": "Write a safety checklist for a warehouse robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000257", "instruction": "Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000014", "instruction": "Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000460", "instruction": "Write a safety checklist for a mobile robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000486", "instruction": "Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000290", "instruction": "Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000414", "instruction": "Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000219", "instruction": "Write a safety checklist for a humanoid during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "first autonomous run after firmware update", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000239", "instruction": "Write a safety checklist for a mobile robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000227", "instruction": "Write a safety checklist for a drone during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000524", "instruction": "Write a safety checklist for a industrial arm during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000367", "instruction": "Write a safety checklist for a service robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000667", "instruction": "Write a safety checklist for a warehouse robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000453", "instruction": "Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000481", "instruction": "Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000561", "instruction": "Write a safety checklist for a industrial arm during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000210", "instruction": "Write a safety checklist for a service robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000505", "instruction": "Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000519", "instruction": "Write a safety checklist for a service robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000066", "instruction": "Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000535", "instruction": "Write a safety checklist for a lab robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000515", "instruction": "Write a safety checklist for a service robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000604", "instruction": "Write a safety checklist for a lab robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000213", "instruction": "Write a safety checklist for a lab robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000312", "instruction": "Write a safety checklist for a lab robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "lifting a near-max payload", "difficulty": "hard", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000207", "instruction": "Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000035", "instruction": "Write a safety checklist for a lab robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000738", "instruction": "Write a safety checklist for a warehouse robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "medium", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000277", "instruction": "Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "first autonomous run after firmware update", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000392", "instruction": "Write a safety checklist for a mobile robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000108", "instruction": "Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000122", "instruction": "Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000573", "instruction": "Write a safety checklist for a service robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000566", "instruction": "Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000435", "instruction": "Write a safety checklist for a mobile robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "first autonomous run after firmware update", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000657", "instruction": "Write a safety checklist for a mobile robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "night shift operation with limited supervision", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000021", "instruction": "Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "night shift operation with limited supervision", "difficulty": "hard", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000201", "instruction": "Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "operating near humans in a shared workspace", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000272", "instruction": "Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000763", "instruction": "Write a safety checklist for a lab robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000126", "instruction": "Write a safety checklist for a service robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000502", "instruction": "Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000139", "instruction": "Write a safety checklist for a mobile robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "hard", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000464", "instruction": "Write a safety checklist for a lab robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000550", "instruction": "Write a safety checklist for a mobile robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000336", "instruction": "Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "first autonomous run after firmware update", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000242", "instruction": "Write a safety checklist for a warehouse robot during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000723", "instruction": "Write a safety checklist for a humanoid during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000114", "instruction": "Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "first autonomous run after firmware update", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000359", "instruction": "Write a safety checklist for a humanoid during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000327", "instruction": "Write a safety checklist for a industrial arm during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000276", "instruction": "Write a safety checklist for a service robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000465", "instruction": "Write a safety checklist for a service robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000521", "instruction": "Write a safety checklist for a humanoid during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "first autonomous run after firmware update", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000628", "instruction": "Write a safety checklist for a drone during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000284", "instruction": "Write a safety checklist for a humanoid during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000549", "instruction": "Write a safety checklist for a drone during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "night shift operation with limited supervision", "difficulty": "medium", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000517", "instruction": "Write a safety checklist for a lab robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "medium", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000779", "instruction": "Write a safety checklist for a lab robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000177", "instruction": "Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "first autonomous run after firmware update", "difficulty": "hard", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000583", "instruction": "Write a safety checklist for a warehouse robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000003", "instruction": "Write a safety checklist for a drone during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "drone", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000708", "instruction": "Write a safety checklist for a mobile robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "mobile_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Do not bypass safety interlocks; confirm payload limits."} | |
| {"id": "rs_000641", "instruction": "Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000621", "instruction": "Write a safety checklist for a warehouse robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000675", "instruction": "Write a safety checklist for a humanoid during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000774", "instruction": "Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000711", "instruction": "Write a safety checklist for a industrial arm during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "lifting a near-max payload", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000266", "instruction": "Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000411", "instruction": "Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "operating near humans in a shared workspace", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000507", "instruction": "Write a safety checklist for a industrial arm during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "operating near humans in a shared workspace", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000428", "instruction": "Write a safety checklist for a warehouse robot during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000045", "instruction": "Write a safety checklist for a industrial arm during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000588", "instruction": "Write a safety checklist for a humanoid during: testing new PID gains on real hardware. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "humanoid", "scenario": "testing new PID gains on real hardware", "difficulty": "easy", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000421", "instruction": "Write a safety checklist for a industrial arm during: first autonomous run after firmware update. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "industrial_arm", "scenario": "first autonomous run after firmware update", "difficulty": "medium", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000589", "instruction": "Write a safety checklist for a service robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "lifting a near-max payload", "difficulty": "medium", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000022", "instruction": "Write a safety checklist for a service robot during: lifting a near-max payload. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "lifting a near-max payload", "difficulty": "hard", "safety_notes": "Test in simulation first; use low speed limits on real hardware."} | |
| {"id": "rs_000216", "instruction": "Write a safety checklist for a service robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "service_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "medium", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |
| {"id": "rs_000324", "instruction": "Write a safety checklist for a lab robot during: operating near humans in a shared workspace. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "lab_robot", "scenario": "operating near humans in a shared workspace", "difficulty": "medium", "safety_notes": "Ensure area is clear; follow lockout/tagout where applicable."} | |
| {"id": "rs_000606", "instruction": "Write a safety checklist for a warehouse robot during: night shift operation with limited supervision. Keep it actionable.", "context": "Checklist should include: environment checks, hardware checks, software checks, operator readiness, abort criteria.\nDo not include anything that bypasses safety interlocks.", "expected_output": "Environment: clear area, mark exclusion zone, confirm lighting/visibility, remove trip hazards.\nHardware: verify E-stop, brakes, interlocks, sensors, battery/power, payload secure, no loose cables.\nSoftware: confirm correct firmware/version, parameter set, speed/torque limits, watchdogs enabled, logging on.\nOperator: assign roles, confirm manual override/teleop ready, review hand signals/radio, confirm PPE if needed.\nTest protocol: start in sim (if available), then low-speed dry run, then incremental escalation with checkpoints.\nAbort criteria: unexpected motion, sensor faults, rising temps/currents, localization loss, collision proximity breach.\nPost-run: power down safely, save logs, document anomalies and corrective actions.", "robot_domain": "warehouse_robot", "scenario": "night shift operation with limited supervision", "difficulty": "easy", "safety_notes": "Keep clear of pinch points; verify E-stop is functional."} | |