urml-conformance 0.5.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- urml_conformance-0.5.0/.gitignore +114 -0
- urml_conformance-0.5.0/CONFORMANCE_KIT.md +166 -0
- urml_conformance-0.5.0/PKG-INFO +207 -0
- urml_conformance-0.5.0/README.md +174 -0
- urml_conformance-0.5.0/fixtures/actuation/01_set_output_digital_positive.yaml +29 -0
- urml_conformance-0.5.0/fixtures/actuation/02_set_output_analog_positive.yaml +25 -0
- urml_conformance-0.5.0/fixtures/actuation/03_set_output_undeclared_line_rejected.yaml +22 -0
- urml_conformance-0.5.0/fixtures/actuation/04_set_output_analog_out_of_range_rejected.yaml +21 -0
- urml_conformance-0.5.0/fixtures/actuation/05_set_output_digital_type_mismatch_rejected.yaml +21 -0
- urml_conformance-0.5.0/fixtures/av/01_plan_follow_positive.yaml +32 -0
- urml_conformance-0.5.0/fixtures/av/02_plan_path_no_hd_map_rejected.yaml +22 -0
- urml_conformance-0.5.0/fixtures/av/03_follow_over_odd_cap_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/av/04_follow_wrong_binding_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/biped/01_digit_patrol_positive.yaml +32 -0
- urml_conformance-0.5.0/fixtures/biped/02_optimus_manifest_accepted.yaml +23 -0
- urml_conformance-0.5.0/fixtures/biped/03_figure_manifest_accepted.yaml +20 -0
- urml_conformance-0.5.0/fixtures/biped/04_apollo_manifest_accepted.yaml +20 -0
- urml_conformance-0.5.0/fixtures/biped/05_neo_manifest_accepted.yaml +21 -0
- urml_conformance-0.5.0/fixtures/biped/06_digit_bimanual_lift_positive.yaml +35 -0
- urml_conformance-0.5.0/fixtures/biped/07_digit_arm_addressed_positive.yaml +29 -0
- urml_conformance-0.5.0/fixtures/biped/08_arm_not_declared_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/biped/09_digit_wholebody_carry_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/biped/10_wholebody_cannot_carry_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/biped/11_wholebody_leg_count_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/biped/12_wholebody_unstable_com_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/biped/13_unitree_g1_retarget_positive.yaml +29 -0
- urml_conformance-0.5.0/fixtures/biped/14_unitree_g1_unstable_retarget_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/biped/15_bimanual_force_over_envelope_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/biped/16_bimanual_gentle_positive.yaml +32 -0
- urml_conformance-0.5.0/fixtures/compliance/01_hbom_clean_accepted.yaml +23 -0
- urml_conformance-0.5.0/fixtures/compliance/02_hbom_cn_chip_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/compliance/03_hbom_vendor_of_vendor_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/compliance/04_evidence_advisory_accepted.yaml +22 -0
- urml_conformance-0.5.0/fixtures/compliance/05_evidence_required_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/deployment/01_commercial_gated_rejected.yaml +18 -0
- urml_conformance-0.5.0/fixtures/deployment/02_noncommercial_gated_accepted.yaml +16 -0
- urml_conformance-0.5.0/fixtures/deployment/03_commercial_gated_no_policy_accepted.yaml +17 -0
- urml_conformance-0.5.0/fixtures/drone/01_inspect_roof_positive.yaml +38 -0
- urml_conformance-0.5.0/fixtures/drone/02_altitude_exceeded_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/drone/03_ground_robot_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/drone/04_hover_positive.yaml +33 -0
- urml_conformance-0.5.0/fixtures/drone/05_scan_positive.yaml +38 -0
- urml_conformance-0.5.0/fixtures/drone/06_measure_positive.yaml +33 -0
- urml_conformance-0.5.0/fixtures/drone/07_geofence_violation_rejected.yaml +30 -0
- urml_conformance-0.5.0/fixtures/drone/08_altitude_band_violation_rejected.yaml +32 -0
- urml_conformance-0.5.0/fixtures/drone/09_occupancy_zone_intrusion_rejected.yaml +29 -0
- urml_conformance-0.5.0/fixtures/drone/10_link_role_undeclared_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/drone/11_link_loss_no_home_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/drone/12_continue_autonomous_incoherent_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/drone/13_link_loss_rth_positive.yaml +22 -0
- urml_conformance-0.5.0/fixtures/drone/14_flight_only_positive.yaml +42 -0
- urml_conformance-0.5.0/fixtures/drone/15_autopilot_class_missing_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/drone/16_autopilot_class_custom_no_note_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/drone/17_land_undeclared_location_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/drone/18_hover_undeclared_location_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/drone/19_detect_near_undeclared_location_rejected.yaml +29 -0
- urml_conformance-0.5.0/fixtures/drone/20_land_outside_geofence_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/drone/21_land_in_occupancy_zone_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/drone/22_land_at_home_positive.yaml +30 -0
- urml_conformance-0.5.0/fixtures/drone/23_hover_over_outside_geofence_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/drone/24_hover_over_occupancy_zone_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/drone/25_hover_over_above_ceiling_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/drone/26_named_location_above_ceiling_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/drone/27_scan_area_contains_zone_rejected.yaml +32 -0
- urml_conformance-0.5.0/fixtures/drone/28_scan_area_clear_of_zone_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/drone/29_detect_near_outside_geofence_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/drone/30_scan_altitude_exceeded_rejected.yaml +30 -0
- urml_conformance-0.5.0/fixtures/drone/31_scan_area_outside_geofence_rejected.yaml +31 -0
- urml_conformance-0.5.0/fixtures/drone/32_return_to_home_altitude_exceeded_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/drone/33_detect_search_radius_outside_geofence_rejected.yaml +30 -0
- urml_conformance-0.5.0/fixtures/drone/34_detect_search_radius_inside_geofence_positive.yaml +33 -0
- urml_conformance-0.5.0/fixtures/drone/35_payload_winch_delivery_positive.yaml +29 -0
- urml_conformance-0.5.0/fixtures/drone/36_release_mechanism_not_declared_rejected.yaml +29 -0
- urml_conformance-0.5.0/fixtures/drone/37_drop_height_exceeded_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/drone/38_carrying_mass_over_cap_rejected.yaml +31 -0
- urml_conformance-0.5.0/fixtures/educational/01_buggy_patrol_positive.yaml +35 -0
- urml_conformance-0.5.0/fixtures/educational/02_vex_patrol_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/educational/03_lego_patrol_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/educational/04_thymio_patrol_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/educational/05_marty_patrol_positive.yaml +34 -0
- urml_conformance-0.5.0/fixtures/educational/06_petoi_patrol_positive.yaml +44 -0
- urml_conformance-0.5.0/fixtures/educational/07_circuitpython_patrol_positive.yaml +35 -0
- urml_conformance-0.5.0/fixtures/educational/08_minimal_node_led_positive.yaml +21 -0
- urml_conformance-0.5.0/fixtures/educational/09_minimal_node_with_mobility_rejected.yaml +21 -0
- urml_conformance-0.5.0/fixtures/educational/10_minimal_node_undeclared_output_rejected.yaml +22 -0
- urml_conformance-0.5.0/fixtures/educational/11_firmware_descriptor_stm32_positive.yaml +22 -0
- urml_conformance-0.5.0/fixtures/educational/12_firmware_descriptor_esp32_positive.yaml +21 -0
- urml_conformance-0.5.0/fixtures/educational/13_drive_positive.yaml +23 -0
- urml_conformance-0.5.0/fixtures/educational/14_drive_distance_exceeded_rejected.yaml +22 -0
- urml_conformance-0.5.0/fixtures/educational/15_relative_motion_requires_educational_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/fleet/01_courier_to_arm_handoff_positive.yaml +61 -0
- urml_conformance-0.5.0/fixtures/fleet/02_undeclared_member_rejected.yaml +22 -0
- urml_conformance-0.5.0/fixtures/fleet/03_capability_missing_on_member_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/fleet/04_concurrent_shared_workspace_no_barrier_rejected.yaml +31 -0
- urml_conformance-0.5.0/fixtures/fleet/05_barrier_without_peer_link_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/fleet/06_engaged_partners_choreography_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/fleet/07_ground_footprint_overlap_rejected.yaml +20 -0
- urml_conformance-0.5.0/fixtures/fleet/08_air_vertical_separation_accepted.yaml +30 -0
- urml_conformance-0.5.0/fixtures/fleet/09_air_same_altitude_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/fleet/10_water_depth_separation_accepted.yaml +19 -0
- urml_conformance-0.5.0/fixtures/fleet/11_water_same_depth_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/fleet/13_temporal_barrier_deconflicts_accepted.yaml +20 -0
- urml_conformance-0.5.0/fixtures/fleet/16_cross_frame_drone_over_rover_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/fleet/17_cross_frame_drone_high_above_rover_accepted.yaml +19 -0
- urml_conformance-0.5.0/fixtures/flexbe/01_turtle_sequence_positive.yaml +39 -0
- urml_conformance-0.5.0/fixtures/flexbe/02_ur3e_pick_place_positive.yaml +72 -0
- urml_conformance-0.5.0/fixtures/home/01_red_mug_positive.yaml +38 -0
- urml_conformance-0.5.0/fixtures/home/02_red_mug_nav_failure.yaml +34 -0
- urml_conformance-0.5.0/fixtures/home/03_missing_location_rejected.yaml +21 -0
- urml_conformance-0.5.0/fixtures/home/04_branch_on_color.yaml +40 -0
- urml_conformance-0.5.0/fixtures/home/05_retry_until_confidence.yaml +29 -0
- urml_conformance-0.5.0/fixtures/home/06_parallel_first_to_succeed.yaml +25 -0
- urml_conformance-0.5.0/fixtures/home/07_policy_country_denied.yaml +24 -0
- urml_conformance-0.5.0/fixtures/home/08_policy_none_accepts_otherwise_denied.yaml +21 -0
- urml_conformance-0.5.0/fixtures/home/09_policy_vendor_denylist.yaml +21 -0
- urml_conformance-0.5.0/fixtures/home/10_speak_listen_conversation.yaml +54 -0
- urml_conformance-0.5.0/fixtures/home/11_emergency_stop_handling.yaml +30 -0
- urml_conformance-0.5.0/fixtures/home/12_force_ceiling_envelope.yaml +27 -0
- urml_conformance-0.5.0/fixtures/home/13_dock_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/home/14_nav_patrol_positive.yaml +42 -0
- urml_conformance-0.5.0/fixtures/home/15_link_loss_hover_no_station_keeping_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/home/16_link_loss_halt_positive.yaml +21 -0
- urml_conformance-0.5.0/fixtures/home/17_mujoco_sentence_to_motion_positive.yaml +35 -0
- urml_conformance-0.5.0/fixtures/home/18_isaac_sentence_to_motion_positive.yaml +35 -0
- urml_conformance-0.5.0/fixtures/home/19_substrate_rmw_custom_no_note_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/home/20_substrate_qos_keep_last_no_depth_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/home/21_chrono_vehicle_terrain_positive.yaml +38 -0
- urml_conformance-0.5.0/fixtures/home/22_substrate_ipc_iceoryx2_positive.yaml +27 -0
- urml_conformance-0.5.0/fixtures/home/23_substrate_ipc_no_config_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/home/24_substrate_ipc_runtime_on_iceoryx2_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/home/25_substrate_ipc_iceoryx1_no_runtime_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/home/26_substrate_ipc_custom_no_note_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/home/27_realtime_cyclic_positive.yaml +27 -0
- urml_conformance-0.5.0/fixtures/home/28_realtime_watchdog_short_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/home/29_monitorable_property_positive.yaml +22 -0
- urml_conformance-0.5.0/fixtures/home/30_monitorable_parse_error_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/home/31_monitorable_undeclared_signal_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/home/32_release_undeclared_location_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/home/33_move_to_area_outside_geofence_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/home/34_move_to_area_inside_geofence_positive.yaml +26 -0
- urml_conformance-0.5.0/fixtures/home/35_speak_without_speech_output_rejected.yaml +21 -0
- urml_conformance-0.5.0/fixtures/home/36_listen_without_speech_input_rejected.yaml +21 -0
- urml_conformance-0.5.0/fixtures/industrial/01_pick_red_positive.yaml +56 -0
- urml_conformance-0.5.0/fixtures/industrial/02_type_mismatch_rejected.yaml +29 -0
- urml_conformance-0.5.0/fixtures/industrial/03_link_outage_relaxed_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/industrial/04_pick_from_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/05_swap_tool_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/industrial/06_swap_tool_undeclared_service_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/industrial/07_opcua_cell_positive.yaml +65 -0
- urml_conformance-0.5.0/fixtures/industrial/08_cobot_cell_positive.yaml +66 -0
- urml_conformance-0.5.0/fixtures/industrial/09_kawasaki_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/10_staubli_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/11_comau_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/12_mitsubishi_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/13_denso_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/14_doosan_cobot_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/15_techman_cobot_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/16_kinova_cobot_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/17_schunk_gripper_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/18_piab_vacuum_positive.yaml +59 -0
- urml_conformance-0.5.0/fixtures/industrial/19_onrobot_magnetic_positive.yaml +59 -0
- urml_conformance-0.5.0/fixtures/industrial/20_soft_robotics_compliant_positive.yaml +59 -0
- urml_conformance-0.5.0/fixtures/industrial/21_ati_ft_positive.yaml +63 -0
- urml_conformance-0.5.0/fixtures/industrial/22_cognex_vision_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/23_sick_safety_lidar_positive.yaml +63 -0
- urml_conformance-0.5.0/fixtures/industrial/24_autosar_ecu_positive.yaml +64 -0
- urml_conformance-0.5.0/fixtures/industrial/25_robotiq_2f85_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/26_schmalz_vacuum_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/27_festo_dhep_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/28_bota_ft_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/29_hokuyo_lidar_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/30_ouster_3d_lidar_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/31_photoneo_motioncam_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/32_zivid_two_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/33_hyundai_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/34_nachi_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/35_epson_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/36_omron_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/37_hanwha_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/38_mecademic_cobot_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/39_neura_cobot_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/40_kassow_cobot_cell_positive.yaml +60 -0
- urml_conformance-0.5.0/fixtures/industrial/41_yaskawa_cell_positive.yaml +61 -0
- urml_conformance-0.5.0/fixtures/industrial/42_ur_cell_positive.yaml +62 -0
- urml_conformance-0.5.0/fixtures/industrial/43_kuka_cell_positive.yaml +61 -0
- urml_conformance-0.5.0/fixtures/industrial/44_fanuc_cell_positive.yaml +61 -0
- urml_conformance-0.5.0/fixtures/industrial/45_kawasaki_call_program_positive.yaml +42 -0
- urml_conformance-0.5.0/fixtures/industrial/46_call_program_undeclared_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/industrial/47_bimanual_one_arm_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/industrial/48_autosar_ara_com_positive.yaml +30 -0
- urml_conformance-0.5.0/fixtures/industrial/49_autosar_ara_com_incomplete_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/industrial/50_pick_from_force_over_envelope_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/industrial/51_pick_from_force_within_envelope_positive.yaml +39 -0
- urml_conformance-0.5.0/fixtures/industrial/52_move_to_fraction_speed_over_cap_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/industrial/53_move_to_fraction_above_one_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/industrial/54_move_to_fraction_speed_within_cap_positive.yaml +28 -0
- urml_conformance-0.5.0/fixtures/industrial/55_place_at_occupancy_zone_rejected.yaml +33 -0
- urml_conformance-0.5.0/fixtures/industrial/56_pick_from_undeclared_source_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/industrial/57_place_at_undeclared_target_rejected.yaml +31 -0
- urml_conformance-0.5.0/fixtures/language/01_whisper_stt_positive.yaml +15 -0
- urml_conformance-0.5.0/fixtures/language/02_vosk_no_policy_positive.yaml +16 -0
- urml_conformance-0.5.0/fixtures/language/03_vosk_default_policy_rejected.yaml +17 -0
- urml_conformance-0.5.0/fixtures/language/04_full_engines_positive.yaml +16 -0
- urml_conformance-0.5.0/fixtures/language/05_nllb_translation_positive.yaml +15 -0
- urml_conformance-0.5.0/fixtures/licensing/01_clean_boundaries_positive.yaml +17 -0
- urml_conformance-0.5.0/fixtures/licensing/02_vendored_gpl_rejected.yaml +19 -0
- urml_conformance-0.5.0/fixtures/licensing/03_restrictiveness_cap_rejected.yaml +17 -0
- urml_conformance-0.5.0/fixtures/manipulation/01_dexterous_precision_grasp_positive.yaml +23 -0
- urml_conformance-0.5.0/fixtures/manipulation/02_grasp_type_requires_dexterous_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/manipulation/03_grasp_type_not_declared_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/manipulation/04_dexterous_grasp_no_type_positive.yaml +23 -0
- urml_conformance-0.5.0/fixtures/manipulation/05_dynamic_target_ballistic_positive.yaml +27 -0
- urml_conformance-0.5.0/fixtures/manipulation/06_target_motion_not_supported_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/manipulation/07_target_motion_mode_not_declared_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/marine/01_survey_positive.yaml +33 -0
- urml_conformance-0.5.0/fixtures/mobile/01_patrol_positive.yaml +32 -0
- urml_conformance-0.5.0/fixtures/mobile/02_hesai_component_denied.yaml +24 -0
- urml_conformance-0.5.0/fixtures/programs/01_declared_intent_positive.yaml +26 -0
- urml_conformance-0.5.0/fixtures/programs/02_declared_intent_unsupported_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/programs/03_declared_intent_unknown_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/quadruped/01_patrol_positive.yaml +33 -0
- urml_conformance-0.5.0/fixtures/quadruped/02_unitree_vendor_denied.yaml +24 -0
- urml_conformance-0.5.0/fixtures/quadruped/03_anymal_patrol_positive.yaml +31 -0
- urml_conformance-0.5.0/fixtures/quadruped/04_ghost_vision60_manifest_accepted.yaml +24 -0
- urml_conformance-0.5.0/fixtures/quadruped/05_spot_arm_pick_positive.yaml +57 -0
- urml_conformance-0.5.0/fixtures/quadruped/06_spot_arm_capture_named_camera_positive.yaml +51 -0
- urml_conformance-0.5.0/fixtures/quadruped/07_spot_arm_capture_undeclared_camera_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/quadruped/08_spot_arm_capture_fixed_camera_target_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/research/01_autoware_manifest_accepted.yaml +28 -0
- urml_conformance-0.5.0/fixtures/rulebook/01_take_off_450ft_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/rulebook/02_take_off_450ft_waiver_accepted.yaml +37 -0
- urml_conformance-0.5.0/fixtures/rulebook/03_capture_in_no_camera_zone_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/rulebook/04_restricted_zone_entry_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/rulebook/05_remote_id_missing_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/rulebook/06_two_aircraft_airborne_rejected.yaml +28 -0
- urml_conformance-0.5.0/fixtures/rulebook/07_policy_none_still_enforced_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/rulebook/08_default_rulebooks_off_accepted.yaml +25 -0
- urml_conformance-0.5.0/fixtures/rulebook/09_over_people_override_zone_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/rulebook/10_capture_at_unknown_place_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/rulebook/11_indoor_lab_switches_off_faa_accepted.yaml +23 -0
- urml_conformance-0.5.0/fixtures/rulebook/12_call_program_not_allowlisted_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/rulebook/13_capture_in_packing_area_accepted.yaml +33 -0
- urml_conformance-0.5.0/fixtures/social/01_reachy_greeting_positive.yaml +42 -0
- urml_conformance-0.5.0/fixtures/social/02_undeclared_gesture_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/social/03_direction_out_of_range_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/social/04_no_expression_block_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/social/05_gesture_requires_social_profile_rejected.yaml +23 -0
- urml_conformance-0.5.0/fixtures/social/06_look_at_beyond_envelope_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/social/07_gesture_over_envelope_duration_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/social/08_gesture_not_allowed_rejected.yaml +24 -0
- urml_conformance-0.5.0/fixtures/social/09_expression_within_envelope_positive.yaml +32 -0
- urml_conformance-0.5.0/fixtures/translation/01_nllb_no_alternative_rejected.yaml +17 -0
- urml_conformance-0.5.0/fixtures/translation/02_nllb_permissive_alternative_accepted.yaml +17 -0
- urml_conformance-0.5.0/fixtures/translation/03_open_llm_primary_accepted.yaml +16 -0
- urml_conformance-0.5.0/fixtures/warehouse/01_pick_from_shelf_place_on_conveyor_positive.yaml +57 -0
- urml_conformance-0.5.0/fixtures/warehouse/02_amr_aisle_dynamic_obstacle_positive.yaml +42 -0
- urml_conformance-0.5.0/fixtures/warehouse/03_handoff_partner_event_undeclared_rejected.yaml +31 -0
- urml_conformance-0.5.0/fixtures/warehouse/04_envelope_speed_violation_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/warehouse/05_people_occupancy_zone_intrusion_rejected.yaml +25 -0
- urml_conformance-0.5.0/fixtures/warehouse/06_handoff_coordination_positive.yaml +64 -0
- urml_conformance-0.5.0/fixtures/warehouse/07_multi_step_amr_cycle_positive.yaml +65 -0
- urml_conformance-0.5.0/fixtures/warehouse/08_compliant_parts_bom_positive.yaml +35 -0
- urml_conformance-0.5.0/fixtures/warehouse/09_pick_from_occupancy_zone_rejected.yaml +29 -0
- urml_conformance-0.5.0/fixtures/warehouse/10_dock_outside_geofence_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/warehouse/11_dock_inside_geofence_positive.yaml +27 -0
- urml_conformance-0.5.0/fixtures/warehouse/12_pick_from_outside_geofence_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/warehouse/13_place_at_outside_geofence_rejected.yaml +31 -0
- urml_conformance-0.5.0/fixtures/warehouse/14_dock_occupancy_zone_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/warehouse/15_pick_from_above_reach_cap_rejected.yaml +27 -0
- urml_conformance-0.5.0/fixtures/warehouse/16_place_at_above_reach_cap_rejected.yaml +32 -0
- urml_conformance-0.5.0/fixtures/warehouse/17_dock_above_reach_cap_rejected.yaml +26 -0
- urml_conformance-0.5.0/fixtures/warehouse/18_low_reach_cycle_positive.yaml +42 -0
- urml_conformance-0.5.0/fixtures/warehouse/19_dock_undeclared_station_rejected.yaml +25 -0
- urml_conformance-0.5.0/llm-bridge/README.md +154 -0
- urml_conformance-0.5.0/llm-bridge/fixtures/home/utterances-en.yaml +30 -0
- urml_conformance-0.5.0/llm-bridge/results/.gitkeep +3 -0
- urml_conformance-0.5.0/llm-bridge/results/2026-06-07/home-echo-double.yaml +17 -0
- urml_conformance-0.5.0/pyproject.toml +79 -0
- urml_conformance-0.5.0/src/urml_conformance/__init__.py +92 -0
- urml_conformance-0.5.0/src/urml_conformance/__main__.py +192 -0
- urml_conformance-0.5.0/src/urml_conformance/_version.py +5 -0
- urml_conformance-0.5.0/src/urml_conformance/fixtures.py +671 -0
- urml_conformance-0.5.0/src/urml_conformance/goal_line.py +246 -0
- urml_conformance-0.5.0/src/urml_conformance/llm_bridge/__init__.py +41 -0
- urml_conformance-0.5.0/src/urml_conformance/llm_bridge/loader.py +150 -0
- urml_conformance-0.5.0/src/urml_conformance/llm_bridge/scorer.py +155 -0
- urml_conformance-0.5.0/src/urml_conformance/py.typed +0 -0
- urml_conformance-0.5.0/src/urml_conformance/registry.py +903 -0
- urml_conformance-0.5.0/src/urml_conformance/report.py +165 -0
- urml_conformance-0.5.0/src/urml_conformance/runner.py +482 -0
- urml_conformance-0.5.0/tests/__init__.py +0 -0
- urml_conformance-0.5.0/tests/test_adapter_protocol.py +129 -0
- urml_conformance-0.5.0/tests/test_bump_version.py +122 -0
- urml_conformance-0.5.0/tests/test_cli.py +120 -0
- urml_conformance-0.5.0/tests/test_conformance_suite.py +198 -0
- urml_conformance-0.5.0/tests/test_envelope_coverage_doc.py +167 -0
- urml_conformance-0.5.0/tests/test_goal_line.py +179 -0
- urml_conformance-0.5.0/tests/test_llm_bridge_loader.py +52 -0
- urml_conformance-0.5.0/tests/test_llm_bridge_scorer.py +102 -0
- urml_conformance-0.5.0/tests/test_outreach_ledger.py +87 -0
- urml_conformance-0.5.0/tests/test_outreach_ledger_schema_v2.py +191 -0
- urml_conformance-0.5.0/tests/test_refresh_audit.py +52 -0
- urml_conformance-0.5.0/tests/test_refresh_commitments.py +52 -0
- urml_conformance-0.5.0/tests/test_registry.py +491 -0
- urml_conformance-0.5.0/tests/test_report.py +179 -0
- urml_conformance-0.5.0/tests/test_rulebook_fixtures.py +97 -0
- urml_conformance-0.5.0/tests/test_sweep_engaged_inbound.py +64 -0
|
@@ -0,0 +1,114 @@
|
|
|
1
|
+
# --- Python ---
|
|
2
|
+
__pycache__/
|
|
3
|
+
*.py[cod]
|
|
4
|
+
*$py.class
|
|
5
|
+
*.so
|
|
6
|
+
.Python
|
|
7
|
+
build/
|
|
8
|
+
dist/
|
|
9
|
+
develop-eggs/
|
|
10
|
+
downloads/
|
|
11
|
+
eggs/
|
|
12
|
+
.eggs/
|
|
13
|
+
lib/
|
|
14
|
+
lib64/
|
|
15
|
+
parts/
|
|
16
|
+
sdist/
|
|
17
|
+
var/
|
|
18
|
+
wheels/
|
|
19
|
+
*.egg-info/
|
|
20
|
+
.installed.cfg
|
|
21
|
+
*.egg
|
|
22
|
+
MANIFEST
|
|
23
|
+
|
|
24
|
+
# Virtual envs
|
|
25
|
+
.venv/
|
|
26
|
+
venv/
|
|
27
|
+
env/
|
|
28
|
+
ENV/
|
|
29
|
+
.python-version
|
|
30
|
+
|
|
31
|
+
# Test / coverage / mypy / pyright
|
|
32
|
+
.coverage
|
|
33
|
+
.coverage.*
|
|
34
|
+
.cache
|
|
35
|
+
.pytest_cache/
|
|
36
|
+
.mypy_cache/
|
|
37
|
+
.dmypy.json
|
|
38
|
+
.pyre/
|
|
39
|
+
.pyright/
|
|
40
|
+
htmlcov/
|
|
41
|
+
nosetests.xml
|
|
42
|
+
coverage.xml
|
|
43
|
+
*.cover
|
|
44
|
+
.hypothesis/
|
|
45
|
+
.tox/
|
|
46
|
+
|
|
47
|
+
# --- Node / web tooling (kept out of core repo; here for safety) ---
|
|
48
|
+
node_modules/
|
|
49
|
+
.pnp.*
|
|
50
|
+
.yarn/cache/
|
|
51
|
+
.yarn/unplugged/
|
|
52
|
+
.yarn/build-state.yml
|
|
53
|
+
.yarn/install-state.gz
|
|
54
|
+
npm-debug.log*
|
|
55
|
+
yarn-debug.log*
|
|
56
|
+
yarn-error.log*
|
|
57
|
+
|
|
58
|
+
# --- C++ / Rust build artifacts (in case reference runtimes land here in early Phase 1) ---
|
|
59
|
+
target/
|
|
60
|
+
*.o
|
|
61
|
+
*.obj
|
|
62
|
+
*.a
|
|
63
|
+
*.lib
|
|
64
|
+
*.dll
|
|
65
|
+
*.dylib
|
|
66
|
+
*.exe
|
|
67
|
+
*.pdb
|
|
68
|
+
cmake-build-*/
|
|
69
|
+
CMakeCache.txt
|
|
70
|
+
CMakeFiles/
|
|
71
|
+
CMakeScripts/
|
|
72
|
+
Testing/
|
|
73
|
+
cmake_install.cmake
|
|
74
|
+
install_manifest.txt
|
|
75
|
+
compile_commands.json
|
|
76
|
+
|
|
77
|
+
# --- ROS 2 build dirs ---
|
|
78
|
+
build/
|
|
79
|
+
install/
|
|
80
|
+
log/
|
|
81
|
+
|
|
82
|
+
# --- Editor and OS junk ---
|
|
83
|
+
.vscode/
|
|
84
|
+
.idea/
|
|
85
|
+
*.swp
|
|
86
|
+
*.swo
|
|
87
|
+
*~
|
|
88
|
+
.DS_Store
|
|
89
|
+
Thumbs.db
|
|
90
|
+
desktop.ini
|
|
91
|
+
|
|
92
|
+
# --- Local-only artifacts ---
|
|
93
|
+
.env
|
|
94
|
+
.env.*
|
|
95
|
+
*.log
|
|
96
|
+
*.tmp
|
|
97
|
+
.local/
|
|
98
|
+
.scratch/
|
|
99
|
+
|
|
100
|
+
# --- Outreach campaign artifacts (operational, not part of the open standard) ---
|
|
101
|
+
# Target lists, message drafts, tracking data, and the launch-approval record
|
|
102
|
+
# stay local. They are private to the maintainer; committing them would
|
|
103
|
+
# telegraph the campaign before launch and could embarrass listed projects.
|
|
104
|
+
outreach/
|
|
105
|
+
|
|
106
|
+
# Outreach dashboard SQLite mirror (RFC-0275). Derived from
|
|
107
|
+
# examples/lighthouses/outreach*.yaml via tools/scripts/refresh_outreach_db.py.
|
|
108
|
+
# Regenerated on demand by `make outreach-refresh`.
|
|
109
|
+
tools/outreach.db
|
|
110
|
+
tools/.outreach.db
|
|
111
|
+
|
|
112
|
+
# Local Claude Code settings (per-machine; permission rules, etc.). Not committed.
|
|
113
|
+
.claude/settings.json
|
|
114
|
+
.claude/settings.local.json
|
|
@@ -0,0 +1,166 @@
|
|
|
1
|
+
<p align="center">
|
|
2
|
+
<a href="https://urml.dev"><img src="https://urml.dev/favicon.svg" alt="URML" width="72" height="72"></a>
|
|
3
|
+
</p>
|
|
4
|
+
|
|
5
|
+
<p align="center">
|
|
6
|
+
A small, opinionated, human-readable language for describing robot intent.
|
|
7
|
+
</p>
|
|
8
|
+
|
|
9
|
+
<p align="center">
|
|
10
|
+
<a href="https://urml.dev"><b>urml.dev</b></a>
|
|
11
|
+
</p>
|
|
12
|
+
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# URML Conformance Kit
|
|
16
|
+
|
|
17
|
+
This is how you check whether a robot runtime is URML-compatible. The
|
|
18
|
+
fixtures in `conformance/fixtures/` are the contract. They are BSL 1.1
|
|
19
|
+
(see [`LICENSING.md`](../LICENSING.md)), and running them to test a
|
|
20
|
+
runtime is free.
|
|
21
|
+
|
|
22
|
+
You do not need any reference runtime, any robot, or ROS to run this.
|
|
23
|
+
The default run is fully hermetic.
|
|
24
|
+
|
|
25
|
+
## The idea in one paragraph
|
|
26
|
+
|
|
27
|
+
URML programs are substrate-neutral. A *runtime* is the thing that
|
|
28
|
+
translates a validated URML program into commands for a specific robot
|
|
29
|
+
stack (ROS 2, PX4/MAVLink, a vendor SDK). A runtime is URML-compatible
|
|
30
|
+
if, for every fixture, it validates the program the way the spec says
|
|
31
|
+
and executes it with the effects the spec says. You demonstrate that by
|
|
32
|
+
implementing one small Python Protocol and running the suite against
|
|
33
|
+
it.
|
|
34
|
+
|
|
35
|
+
## Step 1: implement the adapter Protocol
|
|
36
|
+
|
|
37
|
+
Implement `ROSAdapter` from
|
|
38
|
+
`reference/ros2-runtime/src/urml_ros2_runtime/substrate/base.py`. The
|
|
39
|
+
name has "ROS" in it for historical reasons; the Protocol is
|
|
40
|
+
substrate-neutral and has no ROS dependency. It is ~15 methods, one per
|
|
41
|
+
URML primitive dispatch step (`send_navigation_goal`,
|
|
42
|
+
`send_manipulation_goal`, `query_detection`, ...).
|
|
43
|
+
|
|
44
|
+
Two rules carry all the weight:
|
|
45
|
+
|
|
46
|
+
- **Return failures, do not raise them.** Every method returns a typed
|
|
47
|
+
result with a `success: bool`. A robot-side failure is
|
|
48
|
+
`success=False` with a `reason`. Only an unrecoverable substrate
|
|
49
|
+
break (process died, transport gone) may raise.
|
|
50
|
+
- **Be honest about what you do not have.** If your robot has no arm,
|
|
51
|
+
`send_manipulation_goal` returns `success=False` with a clear
|
|
52
|
+
`reason` (the reference runtimes use a `not_supported_on_<x>`
|
|
53
|
+
convention). It does not pretend.
|
|
54
|
+
|
|
55
|
+
The reference runtimes are worked examples of every shape: a composed
|
|
56
|
+
ROS 2 runtime (`reference/industrial-arm-runtime`,
|
|
57
|
+
`reference/mobile-runtime`), a no-ROS MAVLink runtime
|
|
58
|
+
(`reference/px4-runtime`, `reference/marine-runtime`), and a vendor-SDK
|
|
59
|
+
runtime (`reference/legged-runtime`'s `SpotAdapter` over `bosdyn`).
|
|
60
|
+
Copy the closest one.
|
|
61
|
+
|
|
62
|
+
## Step 2: run the suite against your adapter
|
|
63
|
+
|
|
64
|
+
Your adapter factory is anything callable with no arguments that
|
|
65
|
+
returns a fresh adapter instance. A class or a factory function both
|
|
66
|
+
work:
|
|
67
|
+
|
|
68
|
+
```bash
|
|
69
|
+
pip install -e reference/validator -e reference/ros2-runtime -e conformance
|
|
70
|
+
python -m urml_conformance --adapter your_pkg.substrate:YourAdapter
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Useful flags:
|
|
74
|
+
|
|
75
|
+
```bash
|
|
76
|
+
python -m urml_conformance # hermetic self-test (MockROSAdapter)
|
|
77
|
+
python -m urml_conformance --filter quadruped # one family
|
|
78
|
+
python -m urml_conformance --profile drone # every fixture that lists a profile
|
|
79
|
+
python -m urml_conformance --adapter p:A -v # full per-case report
|
|
80
|
+
python -m urml_conformance --adapter p:A --report report.json # JSON report
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
`urml conformance run --adapter p:A --profile drone --output report.json`
|
|
84
|
+
does the same from the `urml` command line. A registry compatibility claim
|
|
85
|
+
for a profile needs a report that ran every fixture of that profile, which
|
|
86
|
+
is what `--profile` selects.
|
|
87
|
+
|
|
88
|
+
Or wire it in code, the same hook the reference runtimes' gated CI
|
|
89
|
+
uses:
|
|
90
|
+
|
|
91
|
+
```python
|
|
92
|
+
from urml_conformance import ConformanceRunner, run_suite
|
|
93
|
+
report = ConformanceRunner(adapter_factory=lambda: YourAdapter()).run()
|
|
94
|
+
assert report.all_passed, report.render()
|
|
95
|
+
|
|
96
|
+
report = run_suite("your_pkg.substrate:YourAdapter", filter="drone") # what the CLIs run
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
## Step 3: read the result
|
|
100
|
+
|
|
101
|
+
Exit code is `0` only if every selected fixture passes, so this drops
|
|
102
|
+
straight into a CI job. A failing case prints what diverged: a
|
|
103
|
+
validation outcome that did not match, a wrong executed-step count, or
|
|
104
|
+
an audit-trace mismatch. Fixtures whose programs your robot genuinely
|
|
105
|
+
cannot serve (no arm, no camera) are not your failures to force green:
|
|
106
|
+
the right move is the honest not-supported result plus a fixture subset
|
|
107
|
+
that matches your robot's declared capability manifest, exactly as the
|
|
108
|
+
PX4 runtime runs the flight-only subset rather than faking perception.
|
|
109
|
+
|
|
110
|
+
The JSON report (`urml.conformance-report/1`) says what ran:
|
|
111
|
+
`all_passed`, the `passed` and `failed` counts, the `adapter` spec
|
|
112
|
+
(`urml_ros2_runtime:MockROSAdapter` when you pass none), the
|
|
113
|
+
urml-conformance and urml-validator versions, the `--filter` and `--profile`
|
|
114
|
+
selection, the number
|
|
115
|
+
of fixtures, and a sha256 over the fixture files, followed by one result
|
|
116
|
+
per fixture. A report read back must agree with its own results, so an
|
|
117
|
+
edited `all_passed` does not parse.
|
|
118
|
+
|
|
119
|
+
## The goal line: a rejected program sends nothing
|
|
120
|
+
|
|
121
|
+
The main run stops a rejected fixture at the validator. The goal-line
|
|
122
|
+
lane hands every rejected fixture to the runtime itself, through a
|
|
123
|
+
recording proxy around your adapter. A case passes only when the runtime
|
|
124
|
+
refuses, the refusal carries the fixture's expected error codes, and the
|
|
125
|
+
adapter saw zero calls:
|
|
126
|
+
|
|
127
|
+
```bash
|
|
128
|
+
python -m urml_conformance --goal-line # reference runtime + mock
|
|
129
|
+
python -m urml_conformance --goal-line --adapter your_pkg:YourAdapter
|
|
130
|
+
python -m urml_conformance --goal-line --runtime your_pkg:make_runtime
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
`--runtime` takes a callable that receives one adapter and returns your
|
|
134
|
+
runtime. Its `execute(program, manifest, envelope, profiles, *, policy,
|
|
135
|
+
manifest_base_dir)` must refuse by raising an exception whose
|
|
136
|
+
`validation_result` holds the validator's result, the way `URMLRuntime`
|
|
137
|
+
raises `ValidationRejectedError`. Fleet fixtures run through the
|
|
138
|
+
reference `FleetRuntime`. In code, call
|
|
139
|
+
`run_goal_line(adapter_factory=..., runtime_factory=...)`.
|
|
140
|
+
|
|
141
|
+
## What "URML-compatible" means
|
|
142
|
+
|
|
143
|
+
Passing the suite is a factual statement: this runtime reproduces the
|
|
144
|
+
spec's behavior on the shared contract. It is the **self-reported** tier
|
|
145
|
+
of [`spec/conformance/v0.1.0.md`](../spec/conformance/v0.1.0.md) section
|
|
146
|
+
3: run it yourself, in your own CI, against your own runtime's adapter.
|
|
147
|
+
To publish the result, add the JSON report to an entry in the
|
|
148
|
+
[URML registry](../registry/README.md), whose checker refuses a report
|
|
149
|
+
from the mock adapter or with a failed fixture. There is no badge to
|
|
150
|
+
display, and the `URML-Certified` mark is reserved for a separate
|
|
151
|
+
program that does not exist yet (see [TRADEMARK.md](../TRADEMARK.md)).
|
|
152
|
+
|
|
153
|
+
## Privacy
|
|
154
|
+
|
|
155
|
+
The suite runs entirely locally and sends nothing anywhere. There is no
|
|
156
|
+
telemetry, no phone-home, no identifier collected. You can run it fully
|
|
157
|
+
offline.
|
|
158
|
+
|
|
159
|
+
## Contributing a fixture
|
|
160
|
+
|
|
161
|
+
A good fixture is spec-level: it must pass on *any* URML-compatible
|
|
162
|
+
runtime, not just one. If you find behavior the spec implies but no
|
|
163
|
+
fixture pins, that is the most valuable contribution. The fixture
|
|
164
|
+
format is `conformance/fixtures/<profile>/NN_name.yaml`; see existing
|
|
165
|
+
ones for the shape, and send it as a pull request per
|
|
166
|
+
[CONTRIBUTING.md](../CONTRIBUTING.md).
|
|
@@ -0,0 +1,207 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: urml-conformance
|
|
3
|
+
Version: 0.5.0
|
|
4
|
+
Summary: Conformance test suite for URML runtimes. Free, public, runnable.
|
|
5
|
+
Project-URL: Homepage, https://github.com/urml-dev/URML
|
|
6
|
+
Project-URL: Repository, https://github.com/urml-dev/URML
|
|
7
|
+
Project-URL: Issues, https://github.com/urml-dev/URML/issues
|
|
8
|
+
Author: URML Maintainers
|
|
9
|
+
License: BUSL-1.1
|
|
10
|
+
Keywords: conformance,robotics,specification,urml
|
|
11
|
+
Classifier: Development Status :: 3 - Alpha
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: License :: Other/Proprietary License
|
|
14
|
+
Classifier: Operating System :: OS Independent
|
|
15
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
16
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
18
|
+
Classifier: Topic :: Scientific/Engineering
|
|
19
|
+
Requires-Python: >=3.11
|
|
20
|
+
Requires-Dist: pydantic<3,>=2.6
|
|
21
|
+
Requires-Dist: pyyaml<7,>=6.0
|
|
22
|
+
Requires-Dist: urml-ros2-runtime>=0.5.0
|
|
23
|
+
Requires-Dist: urml-validator>=0.5.0
|
|
24
|
+
Provides-Extra: dev
|
|
25
|
+
Requires-Dist: mypy>=1.10; extra == 'dev'
|
|
26
|
+
Requires-Dist: pytest-cov>=5; extra == 'dev'
|
|
27
|
+
Requires-Dist: pytest>=8; extra == 'dev'
|
|
28
|
+
Requires-Dist: ruff>=0.5; extra == 'dev'
|
|
29
|
+
Requires-Dist: types-pyyaml>=6.0; extra == 'dev'
|
|
30
|
+
Provides-Extra: llm-bridge
|
|
31
|
+
Requires-Dist: urml-llm-bridge>=0.5.0; extra == 'llm-bridge'
|
|
32
|
+
Description-Content-Type: text/markdown
|
|
33
|
+
|
|
34
|
+
<p align="center">
|
|
35
|
+
<a href="https://urml.dev"><img src="https://urml.dev/favicon.svg" alt="URML" width="72" height="72"></a>
|
|
36
|
+
</p>
|
|
37
|
+
|
|
38
|
+
<p align="center">
|
|
39
|
+
A small, opinionated, human-readable language for describing robot intent.
|
|
40
|
+
</p>
|
|
41
|
+
|
|
42
|
+
<p align="center">
|
|
43
|
+
<a href="https://urml.dev"><b>urml.dev</b></a>
|
|
44
|
+
</p>
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
# URML Conformance Suite
|
|
49
|
+
|
|
50
|
+
**Status:** v0.1 shipped. **Declarative fixture model + ConformanceRunner + 7 fixture cases + parametrized pytest harness** at pre-alpha `0.1.0a0`. Pulls earlier from the [MANIFESTO Roadmap](../MANIFESTO.md) (which named Phase 3 for the suite v1) so that every URML-compatible runtime has a target to build toward from day one.
|
|
51
|
+
|
|
52
|
+
## What this is
|
|
53
|
+
|
|
54
|
+
The **freely runnable** set of tests that determines whether a runtime is **URML-compatible**. The conformance suite is the bridge between the abstract specification documents in [`/spec`](../spec/) and a concrete claim of compatibility a robot maker can stand behind.
|
|
55
|
+
|
|
56
|
+
A sibling sub-suite, [`conformance/llm-bridge/`](./llm-bridge/), scores `(model, backend, profile)` triples for the on-device LLM bridge introduced by [RFC-0021](../docs/rfcs/0021-on-device-llm-bridge.md). The runtime sub-suite below answers "does this runtime execute URML correctly"; the LLM-bridge sub-suite answers "how reliably does this model emit URML the validator accepts."
|
|
57
|
+
|
|
58
|
+
The conformance suite is licensed under the Business Source License 1.1 (see [`LICENSING.md`](../LICENSING.md)). Running it to test a runtime is non-production use and is free. The eventual *certification program* — the trademark *URML-Certified* — may be paid; the *tests themselves* remain free, public, and runnable by anyone. This separation is deliberate: it lets URML's compatibility claim be honest (anyone can verify it) while preserving a commercial moat in the surround (the mark is licensed, not the tests).
|
|
59
|
+
|
|
60
|
+
The **normative, human-readable contract** this suite enforces — the six clauses a runtime must satisfy, the two tiers, and the spec-gap loop — is [`spec/conformance/v0.1.0.md`](../spec/conformance/v0.1.0.md) ([RFC-0014](../docs/rfcs/0014-substrate-conformance.md)). This suite is its executable form (clause 6); that document is its written form.
|
|
61
|
+
|
|
62
|
+
## How conformance is structured
|
|
63
|
+
|
|
64
|
+
Conformance is **per-specification-version**, not whole-project. A runtime that passes the Layer-2 v0.1 tests and the home-profile v0.1 tests is conformant to *those* specs at *those* versions, no more and no less. The runtime declares this in its own `CONFORMANCE.md`.
|
|
65
|
+
|
|
66
|
+
```yaml
|
|
67
|
+
declares:
|
|
68
|
+
layer-1-hal: 0.1.0
|
|
69
|
+
layer-2-primitives: 0.1.0
|
|
70
|
+
layer-3-behavior: 0.1.0
|
|
71
|
+
layer-4-nl-grammar: 0.1.0
|
|
72
|
+
profiles:
|
|
73
|
+
home: 0.1.0
|
|
74
|
+
```
|
|
75
|
+
|
|
76
|
+
The conformance suite ships with a runner that, given a runtime and the runtime's declared versions, runs the appropriate test set and emits a structured report.
|
|
77
|
+
|
|
78
|
+
## What the suite tests
|
|
79
|
+
|
|
80
|
+
When drafted, the suite contains tests in three categories:
|
|
81
|
+
|
|
82
|
+
### 1. Static behavior
|
|
83
|
+
|
|
84
|
+
Tests of the validator and the spec itself — independent of any particular runtime. These confirm that a given URML program, manifest, and envelope produce the documented validation outcome.
|
|
85
|
+
|
|
86
|
+
### 2. End-to-end behavior
|
|
87
|
+
|
|
88
|
+
Tests of a runtime, given a manifest and a URML program, in a controlled environment (typically a simulator wired into the runtime). These confirm that the runtime *executes* primitives per their documented semantics — `move_to(kitchen)` actually moves the robot to the kitchen, not to some other place.
|
|
89
|
+
|
|
90
|
+
### 3. Negative tests
|
|
91
|
+
|
|
92
|
+
The most important category. Confirms that the runtime correctly **rejects** programs that violate declared capability or the safety envelope. Cases include:
|
|
93
|
+
|
|
94
|
+
- Programs that require capabilities not in the manifest.
|
|
95
|
+
- Programs that exceed declared velocity / payload / force / altitude / geofence / cell-perimeter limits.
|
|
96
|
+
- Programs that violate profile-specific constraints (drone `move_to` missing altitude, industrial program requiring motion with safety-door open, home program requiring motion into a declared people-only zone).
|
|
97
|
+
- Programs that violate Layer-3 invariants (untyped variable references, unbounded retries, type-mismatched arguments).
|
|
98
|
+
|
|
99
|
+
A runtime that *executes* one of these programs has a critical conformance bug. The suite makes that bug visible. The goal-line lane (`python -m urml_conformance --goal-line`) hands every rejected fixture to the runtime itself and requires a refusal with the expected codes and zero adapter calls.
|
|
100
|
+
|
|
101
|
+
## What the suite does NOT test
|
|
102
|
+
|
|
103
|
+
- Performance, latency, jitter. Those are runtime concerns, not specification concerns. A separate (non-conformance) benchmarking suite may eventually live in this directory; if so, it is clearly labeled as a benchmark, not a conformance test.
|
|
104
|
+
- Substrate-specific behavior. The suite tests *URML* compliance; it does not test that the runtime's chosen Layer-0 (ROS 2, PX4, ...) is also well-behaved.
|
|
105
|
+
- Hardware-specific behavior. The suite runs against simulators where possible. Hardware-in-the-loop is the runtime developer's own responsibility.
|
|
106
|
+
|
|
107
|
+
## How conformance is consumed
|
|
108
|
+
|
|
109
|
+
Two paths:
|
|
110
|
+
|
|
111
|
+
1. **Self-reported conformance.** A runtime developer runs the suite against their runtime, records the result, and publishes the report. This is what the open ecosystem looks like. Self-reporting is honest because anyone can re-run the suite and verify.
|
|
112
|
+
2. **Certified conformance** (future, Phase 3+). The URML organization (or its successor foundation) operates a paid program that issues the **URML-Certified** mark to runtimes that pass the suite. The mark is the commercial product; the test is the open standard.
|
|
113
|
+
|
|
114
|
+
## How tests are added
|
|
115
|
+
|
|
116
|
+
A spec change (RFC) that affects observable behavior must land with the corresponding conformance-suite changes in the same release. A spec change without conformance updates is incomplete and is sent back. This rule is what keeps the spec and the suite from drifting.
|
|
117
|
+
|
|
118
|
+
## Status as of Phase 0
|
|
119
|
+
|
|
120
|
+
This directory contains only this README. Drafting the suite begins in Phase 3, after the first reference runtimes have stabilized. Before then, runtimes self-test against the spec documents directly; the formal harness lands once there is enough surface to test.
|
|
121
|
+
|
|
122
|
+
## Quickstart (v0.1 — hermetic, no ROS 2 needed)
|
|
123
|
+
|
|
124
|
+
```bash
|
|
125
|
+
cd conformance
|
|
126
|
+
python -m venv .venv && . .venv/bin/activate # Windows: .venv\Scripts\activate
|
|
127
|
+
pip install -e ../reference/validator
|
|
128
|
+
pip install -e ../reference/ros2-runtime
|
|
129
|
+
pip install -e ".[dev]"
|
|
130
|
+
pytest
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
Use the runner programmatically:
|
|
134
|
+
|
|
135
|
+
```python
|
|
136
|
+
from urml_conformance import ConformanceRunner
|
|
137
|
+
|
|
138
|
+
runner = ConformanceRunner()
|
|
139
|
+
report = runner.run()
|
|
140
|
+
assert report.all_passed, report.render()
|
|
141
|
+
```
|
|
142
|
+
|
|
143
|
+
Check that every rejected fixture sends zero commands through the runtime:
|
|
144
|
+
|
|
145
|
+
```bash
|
|
146
|
+
python -m urml_conformance --goal-line
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
## Authoring a new fixture
|
|
150
|
+
|
|
151
|
+
Drop a YAML file under `conformance/fixtures/<profile>/`:
|
|
152
|
+
|
|
153
|
+
```yaml
|
|
154
|
+
name: profile/my_case
|
|
155
|
+
description: One-line summary.
|
|
156
|
+
manifest: turtlebot4_home # name from MANIFEST_REGISTRY
|
|
157
|
+
envelope: home_default # optional; name from ENVELOPE_REGISTRY
|
|
158
|
+
profiles: [home]
|
|
159
|
+
|
|
160
|
+
program:
|
|
161
|
+
profile: home
|
|
162
|
+
behavior:
|
|
163
|
+
type: sequence
|
|
164
|
+
steps: [ ... ]
|
|
165
|
+
|
|
166
|
+
adapter_overrides: # optional: pre-configure MockROSAdapter
|
|
167
|
+
navigation: { success: false, reason: path_blocked }
|
|
168
|
+
|
|
169
|
+
expected_validation:
|
|
170
|
+
accepted: true # or false + error_codes for rejection tests
|
|
171
|
+
|
|
172
|
+
expected_execution: # omit for validator-only cases
|
|
173
|
+
success: true
|
|
174
|
+
steps_executed: 5
|
|
175
|
+
audit_methods: [send_navigation_goal, ...]
|
|
176
|
+
bindings_contains:
|
|
177
|
+
target_mug: { class: mug }
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
The fixture is picked up automatically by `discover_fixtures()` and exercised by the next `pytest` run.
|
|
181
|
+
|
|
182
|
+
## What's in the v0.1 fixture set
|
|
183
|
+
|
|
184
|
+
A representative selection (the full set is discovered automatically from
|
|
185
|
+
`conformance/fixtures/**/*.yaml` by `discover_fixtures()` and has grown well
|
|
186
|
+
beyond the rows below as profiles and runtimes landed — run `urml conformance
|
|
187
|
+
run` for the live count):
|
|
188
|
+
|
|
189
|
+
| Fixture | Exercises |
|
|
190
|
+
|---|---|
|
|
191
|
+
| `home/red_mug_positive` | Canonical red-mug fetch end to end. |
|
|
192
|
+
| `home/red_mug_nav_failure` | Adapter failure → `abort_and_report` halts the sequence. |
|
|
193
|
+
| `home/missing_location_rejected` | Validator-only: undeclared location → `capability.missing_location`. |
|
|
194
|
+
| `home/branch_on_color` | Branch composition + `$ref.field.subfield` condition evaluation. |
|
|
195
|
+
| `home/retry_until_confidence` | Retry composition with `until` short-circuit. |
|
|
196
|
+
| `home/parallel_first_to_succeed` | Parallel composition with `first_to_succeed` mode. |
|
|
197
|
+
| `industrial/pick_red_positive` | Industrial pick-and-place written with the core twelve (composition-equivalent). |
|
|
198
|
+
| `industrial/pick_from_positive` | RFC-0013: `pick_from` + `place_at`; the picked-object binding flows between them. |
|
|
199
|
+
| `industrial/swap_tool_positive` | RFC-0013: `swap_tool` rides the docking-service path (`send_docking_goal`). |
|
|
200
|
+
| `industrial/swap_tool_undeclared_service_rejected` | RFC-0013 negative: `swap_tool` at a non-station → `capability.missing_docking_station`. |
|
|
201
|
+
|
|
202
|
+
## Related documents
|
|
203
|
+
|
|
204
|
+
- [`LICENSING.md`](../LICENSING.md): what is free and what needs a commercial license.
|
|
205
|
+
- [`/spec/`](../spec/) — the specifications the suite tests against.
|
|
206
|
+
- [`/reference/`](../reference/) — the reference implementations the suite is first exercised against.
|
|
207
|
+
- [`MANIFESTO.md`](../MANIFESTO.md) §License Direction — the trademark / conformance-mark policy that lives separately from the suite.
|
|
@@ -0,0 +1,174 @@
|
|
|
1
|
+
<p align="center">
|
|
2
|
+
<a href="https://urml.dev"><img src="https://urml.dev/favicon.svg" alt="URML" width="72" height="72"></a>
|
|
3
|
+
</p>
|
|
4
|
+
|
|
5
|
+
<p align="center">
|
|
6
|
+
A small, opinionated, human-readable language for describing robot intent.
|
|
7
|
+
</p>
|
|
8
|
+
|
|
9
|
+
<p align="center">
|
|
10
|
+
<a href="https://urml.dev"><b>urml.dev</b></a>
|
|
11
|
+
</p>
|
|
12
|
+
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# URML Conformance Suite
|
|
16
|
+
|
|
17
|
+
**Status:** v0.1 shipped. **Declarative fixture model + ConformanceRunner + 7 fixture cases + parametrized pytest harness** at pre-alpha `0.1.0a0`. Pulls earlier from the [MANIFESTO Roadmap](../MANIFESTO.md) (which named Phase 3 for the suite v1) so that every URML-compatible runtime has a target to build toward from day one.
|
|
18
|
+
|
|
19
|
+
## What this is
|
|
20
|
+
|
|
21
|
+
The **freely runnable** set of tests that determines whether a runtime is **URML-compatible**. The conformance suite is the bridge between the abstract specification documents in [`/spec`](../spec/) and a concrete claim of compatibility a robot maker can stand behind.
|
|
22
|
+
|
|
23
|
+
A sibling sub-suite, [`conformance/llm-bridge/`](./llm-bridge/), scores `(model, backend, profile)` triples for the on-device LLM bridge introduced by [RFC-0021](../docs/rfcs/0021-on-device-llm-bridge.md). The runtime sub-suite below answers "does this runtime execute URML correctly"; the LLM-bridge sub-suite answers "how reliably does this model emit URML the validator accepts."
|
|
24
|
+
|
|
25
|
+
The conformance suite is licensed under the Business Source License 1.1 (see [`LICENSING.md`](../LICENSING.md)). Running it to test a runtime is non-production use and is free. The eventual *certification program* — the trademark *URML-Certified* — may be paid; the *tests themselves* remain free, public, and runnable by anyone. This separation is deliberate: it lets URML's compatibility claim be honest (anyone can verify it) while preserving a commercial moat in the surround (the mark is licensed, not the tests).
|
|
26
|
+
|
|
27
|
+
The **normative, human-readable contract** this suite enforces — the six clauses a runtime must satisfy, the two tiers, and the spec-gap loop — is [`spec/conformance/v0.1.0.md`](../spec/conformance/v0.1.0.md) ([RFC-0014](../docs/rfcs/0014-substrate-conformance.md)). This suite is its executable form (clause 6); that document is its written form.
|
|
28
|
+
|
|
29
|
+
## How conformance is structured
|
|
30
|
+
|
|
31
|
+
Conformance is **per-specification-version**, not whole-project. A runtime that passes the Layer-2 v0.1 tests and the home-profile v0.1 tests is conformant to *those* specs at *those* versions, no more and no less. The runtime declares this in its own `CONFORMANCE.md`.
|
|
32
|
+
|
|
33
|
+
```yaml
|
|
34
|
+
declares:
|
|
35
|
+
layer-1-hal: 0.1.0
|
|
36
|
+
layer-2-primitives: 0.1.0
|
|
37
|
+
layer-3-behavior: 0.1.0
|
|
38
|
+
layer-4-nl-grammar: 0.1.0
|
|
39
|
+
profiles:
|
|
40
|
+
home: 0.1.0
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
The conformance suite ships with a runner that, given a runtime and the runtime's declared versions, runs the appropriate test set and emits a structured report.
|
|
44
|
+
|
|
45
|
+
## What the suite tests
|
|
46
|
+
|
|
47
|
+
When drafted, the suite contains tests in three categories:
|
|
48
|
+
|
|
49
|
+
### 1. Static behavior
|
|
50
|
+
|
|
51
|
+
Tests of the validator and the spec itself — independent of any particular runtime. These confirm that a given URML program, manifest, and envelope produce the documented validation outcome.
|
|
52
|
+
|
|
53
|
+
### 2. End-to-end behavior
|
|
54
|
+
|
|
55
|
+
Tests of a runtime, given a manifest and a URML program, in a controlled environment (typically a simulator wired into the runtime). These confirm that the runtime *executes* primitives per their documented semantics — `move_to(kitchen)` actually moves the robot to the kitchen, not to some other place.
|
|
56
|
+
|
|
57
|
+
### 3. Negative tests
|
|
58
|
+
|
|
59
|
+
The most important category. Confirms that the runtime correctly **rejects** programs that violate declared capability or the safety envelope. Cases include:
|
|
60
|
+
|
|
61
|
+
- Programs that require capabilities not in the manifest.
|
|
62
|
+
- Programs that exceed declared velocity / payload / force / altitude / geofence / cell-perimeter limits.
|
|
63
|
+
- Programs that violate profile-specific constraints (drone `move_to` missing altitude, industrial program requiring motion with safety-door open, home program requiring motion into a declared people-only zone).
|
|
64
|
+
- Programs that violate Layer-3 invariants (untyped variable references, unbounded retries, type-mismatched arguments).
|
|
65
|
+
|
|
66
|
+
A runtime that *executes* one of these programs has a critical conformance bug. The suite makes that bug visible. The goal-line lane (`python -m urml_conformance --goal-line`) hands every rejected fixture to the runtime itself and requires a refusal with the expected codes and zero adapter calls.
|
|
67
|
+
|
|
68
|
+
## What the suite does NOT test
|
|
69
|
+
|
|
70
|
+
- Performance, latency, jitter. Those are runtime concerns, not specification concerns. A separate (non-conformance) benchmarking suite may eventually live in this directory; if so, it is clearly labeled as a benchmark, not a conformance test.
|
|
71
|
+
- Substrate-specific behavior. The suite tests *URML* compliance; it does not test that the runtime's chosen Layer-0 (ROS 2, PX4, ...) is also well-behaved.
|
|
72
|
+
- Hardware-specific behavior. The suite runs against simulators where possible. Hardware-in-the-loop is the runtime developer's own responsibility.
|
|
73
|
+
|
|
74
|
+
## How conformance is consumed
|
|
75
|
+
|
|
76
|
+
Two paths:
|
|
77
|
+
|
|
78
|
+
1. **Self-reported conformance.** A runtime developer runs the suite against their runtime, records the result, and publishes the report. This is what the open ecosystem looks like. Self-reporting is honest because anyone can re-run the suite and verify.
|
|
79
|
+
2. **Certified conformance** (future, Phase 3+). The URML organization (or its successor foundation) operates a paid program that issues the **URML-Certified** mark to runtimes that pass the suite. The mark is the commercial product; the test is the open standard.
|
|
80
|
+
|
|
81
|
+
## How tests are added
|
|
82
|
+
|
|
83
|
+
A spec change (RFC) that affects observable behavior must land with the corresponding conformance-suite changes in the same release. A spec change without conformance updates is incomplete and is sent back. This rule is what keeps the spec and the suite from drifting.
|
|
84
|
+
|
|
85
|
+
## Status as of Phase 0
|
|
86
|
+
|
|
87
|
+
This directory contains only this README. Drafting the suite begins in Phase 3, after the first reference runtimes have stabilized. Before then, runtimes self-test against the spec documents directly; the formal harness lands once there is enough surface to test.
|
|
88
|
+
|
|
89
|
+
## Quickstart (v0.1 — hermetic, no ROS 2 needed)
|
|
90
|
+
|
|
91
|
+
```bash
|
|
92
|
+
cd conformance
|
|
93
|
+
python -m venv .venv && . .venv/bin/activate # Windows: .venv\Scripts\activate
|
|
94
|
+
pip install -e ../reference/validator
|
|
95
|
+
pip install -e ../reference/ros2-runtime
|
|
96
|
+
pip install -e ".[dev]"
|
|
97
|
+
pytest
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
Use the runner programmatically:
|
|
101
|
+
|
|
102
|
+
```python
|
|
103
|
+
from urml_conformance import ConformanceRunner
|
|
104
|
+
|
|
105
|
+
runner = ConformanceRunner()
|
|
106
|
+
report = runner.run()
|
|
107
|
+
assert report.all_passed, report.render()
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
Check that every rejected fixture sends zero commands through the runtime:
|
|
111
|
+
|
|
112
|
+
```bash
|
|
113
|
+
python -m urml_conformance --goal-line
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
## Authoring a new fixture
|
|
117
|
+
|
|
118
|
+
Drop a YAML file under `conformance/fixtures/<profile>/`:
|
|
119
|
+
|
|
120
|
+
```yaml
|
|
121
|
+
name: profile/my_case
|
|
122
|
+
description: One-line summary.
|
|
123
|
+
manifest: turtlebot4_home # name from MANIFEST_REGISTRY
|
|
124
|
+
envelope: home_default # optional; name from ENVELOPE_REGISTRY
|
|
125
|
+
profiles: [home]
|
|
126
|
+
|
|
127
|
+
program:
|
|
128
|
+
profile: home
|
|
129
|
+
behavior:
|
|
130
|
+
type: sequence
|
|
131
|
+
steps: [ ... ]
|
|
132
|
+
|
|
133
|
+
adapter_overrides: # optional: pre-configure MockROSAdapter
|
|
134
|
+
navigation: { success: false, reason: path_blocked }
|
|
135
|
+
|
|
136
|
+
expected_validation:
|
|
137
|
+
accepted: true # or false + error_codes for rejection tests
|
|
138
|
+
|
|
139
|
+
expected_execution: # omit for validator-only cases
|
|
140
|
+
success: true
|
|
141
|
+
steps_executed: 5
|
|
142
|
+
audit_methods: [send_navigation_goal, ...]
|
|
143
|
+
bindings_contains:
|
|
144
|
+
target_mug: { class: mug }
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
The fixture is picked up automatically by `discover_fixtures()` and exercised by the next `pytest` run.
|
|
148
|
+
|
|
149
|
+
## What's in the v0.1 fixture set
|
|
150
|
+
|
|
151
|
+
A representative selection (the full set is discovered automatically from
|
|
152
|
+
`conformance/fixtures/**/*.yaml` by `discover_fixtures()` and has grown well
|
|
153
|
+
beyond the rows below as profiles and runtimes landed — run `urml conformance
|
|
154
|
+
run` for the live count):
|
|
155
|
+
|
|
156
|
+
| Fixture | Exercises |
|
|
157
|
+
|---|---|
|
|
158
|
+
| `home/red_mug_positive` | Canonical red-mug fetch end to end. |
|
|
159
|
+
| `home/red_mug_nav_failure` | Adapter failure → `abort_and_report` halts the sequence. |
|
|
160
|
+
| `home/missing_location_rejected` | Validator-only: undeclared location → `capability.missing_location`. |
|
|
161
|
+
| `home/branch_on_color` | Branch composition + `$ref.field.subfield` condition evaluation. |
|
|
162
|
+
| `home/retry_until_confidence` | Retry composition with `until` short-circuit. |
|
|
163
|
+
| `home/parallel_first_to_succeed` | Parallel composition with `first_to_succeed` mode. |
|
|
164
|
+
| `industrial/pick_red_positive` | Industrial pick-and-place written with the core twelve (composition-equivalent). |
|
|
165
|
+
| `industrial/pick_from_positive` | RFC-0013: `pick_from` + `place_at`; the picked-object binding flows between them. |
|
|
166
|
+
| `industrial/swap_tool_positive` | RFC-0013: `swap_tool` rides the docking-service path (`send_docking_goal`). |
|
|
167
|
+
| `industrial/swap_tool_undeclared_service_rejected` | RFC-0013 negative: `swap_tool` at a non-station → `capability.missing_docking_station`. |
|
|
168
|
+
|
|
169
|
+
## Related documents
|
|
170
|
+
|
|
171
|
+
- [`LICENSING.md`](../LICENSING.md): what is free and what needs a commercial license.
|
|
172
|
+
- [`/spec/`](../spec/) — the specifications the suite tests against.
|
|
173
|
+
- [`/reference/`](../reference/) — the reference implementations the suite is first exercised against.
|
|
174
|
+
- [`MANIFESTO.md`](../MANIFESTO.md) §License Direction — the trademark / conformance-mark policy that lives separately from the suite.
|