Gazebo vs ROS 2

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Gazebo—none0/10

   Direct probes show no llms.txt (404), no markdown-alt docs, and no OpenAPI spec, indicating no agent-oriented documentation format is provided; no evidence of any agent-discoverable docs endpoint.

   • [probe] “PROBE llms.txt: HTTP 404 at https://gazebosim.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://gazebosim.org/docs/latest/getstarted/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”

   proof ↗⚑ flag

   ROS 2—none0/10

   No evidence of an llms.txt file, agent-oriented documentation format, or any mention of AI agent-targeted docs; the evidence pack only covers standard human-oriented ROS 2 documentation and community discussion.

   ⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Gazebo
   Gazebo✓fullclaimed8/10

   Gazebo explicitly supports headless server-only operation via the -s flag and even offers a dedicated lightweight server-only package (gz-sim-server) without GUI/Qt dependencies, plus CLI tools and TCP/IP transport for remote/automated control, all of which are well suited to CI pipelines. Missing for 10: explicit first-party CI/CD example (e.g., GitHub Actions workflow) or independent report confirming headless CI usage in practice.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “the gz-sim10-server package provides a lightweight alternative. It installs only the Gazebo simulation server (gz-sim-server) without any GU…”
   • [claimed-docs] “It installs only the Gazebo simulation server (`gz-sim-server`) without any GUI or Qt dependencies, resulting in a significantly smaller ins…”
   • [github] “Command line tools: Extensive command line tools for increased simulation introspection and control.”
   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”

   proof ↗⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2 documents a headless-capable install (ROS-Base 'Bare Bones' with no GUI tools) plus a full CLI toolset (ros2 command, topic pub, bag record/play) that can be scripted for automation, supporting non-interactive/CI-style operation. However there's no explicit documentation of CI pipelines, Docker images, or automated test harnesses for ROS 2 itself. Missing for 10: explicit CI/automation docs or examples, containerized/headless deployment guidance, and independent evidence of running ROS 2 in a CI pipeline.

   • [claimed-docs] “ROS-Base Install (Bare Bones): Communication libraries, message packages, command line tools. No GUI tools.”
   • [claimed-docs] “ROS 2 includes a suite of command-line tools for introspecting a ROS 2 system.”
   • [claimed-docs] “The main entry point for the tools is the command ros2, which itself has various sub-commands for introspecting and working with nodes, topi…”
   • [claimed-docs] “$ ros2 topic pub /chatter std_msgs/msg/String "data: Hello world"”
   • [claimed-docs] “bag: Record/play a rosbag”
   • [claimed-docs] “ROS 2 runs a background daemon process that maintains information about the ROS graph to provide faster responses to queries, such as the li…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round drawn
   Gazebo—none0/10

   Gazebo is a robotics simulator, not an AI agent, so it is a plausible candidate to expose an official MCP server for agent integration, but no evidence in the pack mentions MCP, agent connectivity, or any AI-agent integration protocol at all.

   ⚑ flag

   ROS 2—none0/10

   ROS 2 is a robotics middleware/framework, not an AI agent — publishing an official MCP server is a plausible ecosystem capability, but no evidence in the pack mentions MCP, agent connectivity, or any AI-agent integration server. Missing for 10: any mention of an official MCP server, MCP protocol support, or agent-facing API for ROS 2.

   ⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to ROS 2
   Gazebo✓fullclaimed7/10

   Gazebo ships an official `gz` CLI with documented commands (e.g. `gz sim shapes.sdf`), headless/server-only mode (`-s` flag) and server-only packages that are ideal for scripted/automated (agentic) invocation without a GUI, plus GitHub docs calling out 'extensive command line tools for increased simulation introspection and control'. Missing for 10: explicit framing of the CLI for AI-agent orchestration use-cases and independent (non-vendor) corroboration of CLI usage in automated pipelines.

   • [claimed-docs] “gz sim shapes.sdf”
   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the `-s` (server only) flag.”
   • [claimed-docs] “the gz-sim10-server package provides a lightweight alternative. It installs only the Gazebo simulation server (gz-sim-server) without any GU…”
   • [github] “Command line tools: Extensive command line tools for increased simulation introspection and control.”
   • [github] “Extensive command line tools for increased simulation introspection and control.”

   proof ↗⚑ flag

   ROS 2✓fullclaimed8/10

   ROS 2 ships an official, extensively documented `ros2` CLI with sub-commands for nodes, topics, services, bags, security, etc., making it fully scriptable and usable by any automated/agentic caller. Missing for 10: explicit documentation or examples targeting AI-agent/automated usage patterns, and independent hands-on confirmation of CLI reliability for such workflows.

   • [claimed-docs] “ROS 2 includes a suite of command-line tools for introspecting a ROS 2 system.”
   • [claimed-docs] “Command-line introspection tools using an extensible framework”
   • [claimed-docs] “The main entry point for the tools is the command ros2, which itself has various sub-commands for introspecting and working with nodes, topi…”
   • [claimed-docs] “ros2 topic pub /chatter std_msgs/msg/String "data: Hello world"”
   • [claimed-docs] “bag: Record/play a rosbag”
   • [claimed-docs] “ROS 2 runs a background daemon process that maintains information about the ROS graph to provide faster responses to queries, such as the li…”
   • [claimed-docs] “$ ros2 topic pub /chatter std_msgs/msg/String "data: Hello world"”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round to ROS 2
   Gazebo~partialprobed5/10

   Gazebo exposes documented, non-GUI ways to drive the simulator programmatically: a headless server mode (-s flag), gz-transport for socket-based TCP/IP message passing to remote-control simulations, extensive CLI tools for introspection/control, and C++ library APIs (gz-math, sdformat, gz-transport) for building custom integrations/plugins. However, probes for a modern machine-readable API spec (OpenAPI/swagger) and an llms.txt all returned 404, and there is no evidence of a REST/HTTP API or AI-specific SDK. missing for 10: OpenAPI/swagger spec or any public HTTP API, explicit AI-agent-oriented API docs or llms.txt, independent confirmation that an AI agent can drive Gazebo via gz-transport.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the `-s` (server only) flag.”
   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Extensive command line tools for increased simulation introspection and control.”
   • [claimed-docs] “those who use individual Gazebo libraries (like `gz-math`, `sdformat`, or `gz-transport`) directly in their own C++ applications”
   • [probe] “PROBE llms.txt: HTTP 404 at https://gazebosim.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”

   proof ↗⚑ flag

   ROS 2✓fullcommunity7/10

   ROS 2 exposes a well-documented public API surface — client libraries in multiple languages (rclpy/rclcpp) for nodes, topics, services, actions, parameters, plus an extensible CLI (`ros2 topic`, `ros2 service`, `ros2 bag`, etc.) and Python APIs for bag recording — all of which let an external program or agent drive the system programmatically. Missing for 10: no explicit mention of AI-agent-specific SDKs, and community commentary flags friction/complexity in actually using these APIs in practice (dependency hell, steep learning curve), so real-world ease for an AI-native driver is unproven.

   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “ROS 2 includes a suite of command-line tools for introspecting a ROS 2 system.”
   • [claimed-docs] “$ ros2 topic pub /chatter std_msgs/msg/String "data: Hello world"”
   • [claimed-docs] “Topics: For continuous data streams. Services: For synchronous request/response interactions. Actions: For long-running tasks with feedback”
   • [claimed-docs] “It also provides a Python API for reading from and writing to a bag from your own source code.”
   • [claimed-docs] “Set/retrieve parameters”
   • [claimed-docs] “The main entry point for the tools is the command ros2, which itself has various sub-commands for introspecting and working with nodes, topi…”
   • [community] “I've been a ROS 1 (and now 2) user since 2010... ROS gives you some important things 'for free' if you cooperate with its ecosystem conventi…”
   • [community] “I'm really struggling in learning ROS in a systematic way. The tutorials are all over the place and somehow unorganized IMO. When trying to …”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to ROS 2
   Gazebo~partialprobed6/10

   Gazebo documents genuine official SDKs/libraries (gz-math, gz-transport, sdformat) and a plugin API for building custom C++ applications/plugins, with a dedicated 'Developers' docs section (gazebo-docs-1/8/14/16). However, evidence shows only C++-centric libraries with no Python or other language SDK bindings, no AI-agent-oriented SDK, and probes show no llms.txt or OpenAPI spec, suggesting no AI-native tooling layer. Missing for 10: language bindings beyond C++/plugins, an AI-agent-specific SDK or API spec, independent developer corroboration of SDK usability.

   • [claimed-docs] “Developers: For those who use individual Gazebo libraries (like gz-math, sdformat, or gz-transport) directly in their own C++ applications, …”
   • [claimed-docs] “those who use individual Gazebo libraries (like `gz-math`, `sdformat`, or `gz-transport`) directly in their own C++ applications”
   • [claimed-docs] “For those who use individual Gazebo libraries (like gz-math, sdformat, or gz-transport) directly in their own C++ applications, or those who…”
   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [claimed-docs] “If your package directly depends on a Gazebo library, instead of relying only on ros_gz, refer to this documentation to learn how to use the…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://gazebosim.org/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”

   proof ↗⚑ flag

   ROS 2✓fullclaimed7/10

   ROS 2 ships official client libraries (rclcpp, rclpy, etc.) that expose the core ROS 2 functionality, letting developers build in the language best suited to their application, and this is the backbone of any ROS 2 application development (ros2-docs-7, ros2-docs-35, ros2-docs-36, ros2-docs-21). This constitutes an official SDK story that any AI-native builder could target when writing perception/planning nodes. Missing for 10: explicit AI-agent-oriented SDK features or examples (e.g., LLM/agent integration guides), broader language coverage beyond C++/Python emphasis, and independent hands-on corroboration of SDK ergonomics.

   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “client libraries expose to users the core functionality that makes ROS "ROS"”
   • [claimed-docs] “you might prefer to write visualization tools in Python because it makes prototyping iterations faster, while for parts of your system that …”

   proof ↗⚑ flag

Agentic features

1. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Gazebo—none0/10

   Gazebo is a robotics simulator controlled via CLI tools, SDF files, and C++ plugins; no evidence of any natural-language command interface, LLM integration, or agentic control layer is present in the evidence pack.

   ⚑ flag

   ROS 2—none0/10

   ROS 2's interfaces are CLI-based (ros2 command with sub-commands) and programmatic client libraries, not natural-language control; no evidence of NL command parsing, LLM integration, or agentic natural-language interface is present in the evidence pack.

   ⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Gazebo—none0/10

   No evidence of an interactive API reference or runnable examples; probes for llms.txt, markdown docs, and OpenAPI specs all returned 404, and the docs are static C++ library documentation without interactive tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://gazebosim.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://gazebosim.org/docs/latest/getstarted/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”

   proof ↗⚑ flag

   ROS 2—none0/10

   The evidence pack shows standard reStructuredText documentation, tutorials, and CLI examples, but nothing describing an interactive API reference (e.g., a searchable/browsable API explorer with runnable/executable code examples in-browser). No mention of interactive docs, sandboxed code execution, or API playgrounds.

   ⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Gazebo—none0/10

   Gazebo is a robotics simulator, not an HTTP API service, and probes explicitly show no OpenAPI/swagger endpoints or llms.txt exist. No evidence of any machine-readable API spec being offered.

   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://gazebosim.org/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://gazebosim.org/docs/latest/getstarted/.md”

   proof ↗⚑ flag

   ROS 2—none0/10

   ROS 2 defines interfaces via .msg/.srv/.action IDL files and provides CLI introspection tools, but no evidence in the pack shows a downloadable machine-readable API spec in OpenAPI or equivalent format for AI-native consumption. missing for 10: any OpenAPI/JSON-schema export, machine-readable spec endpoint, or documented spec-generation tool.

   ⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Gazebo
   Gazebo✓fullclaimed7/10

   Gazebo is fundamentally a robot/environment simulator that lets users test robots, sensors, and physics in a virtual sandbox instead of on real (production) hardware — it can run headless or on remote servers via TCP/IP transport, and supports numerous pre-built simulation models via Gazebo Fuel, letting an AI-native user iterate safely without touching production systems. Missing for 10: explicit framing around isolating from 'production data' (e.g., data provenance, reset/snapshot guarantees) and no first-party mention of AI/agent-specific sandbox workflows.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “the gz-sim10-server package provides a lightweight alternative. It installs only the Gazebo simulation server (gz-sim-server) without any GU…”
   • [github] “Simulation models: Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other p…”
   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Dynamics simulation: Access multiple high-performance physics engines through Gazebo Physics.”

   proof ↗⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2 supports Gazebo simulation (ros2-docs-16) and rosbag recording/playback (ros2-docs-17, ros2-docs-23, ros2-docs-39) which together enable testing against simulated/recorded data instead of live production systems, and separate ROS domains/DDS partitioning could isolate test traffic. However there is no explicit first-party guidance framing a dedicated 'sandbox vs production' workflow or environment isolation for AI-native testing. missing for 10: explicit sandbox/staging environment documentation, guidance on isolating test data from production ROS graphs, AI-agent-specific test harness integration, independent corroboration of safe sandbox testing practice.

   • [claimed-docs] “Launch a Simulation with Gazebo and ROS 2”
   • [claimed-docs] “It also provides a Python API for reading from and writing to a bag from your own source code.”
   • [claimed-docs] “This allows you to subscribe to a topic and save the received data to a bag at the same time as performing any other processing of your choi…”
   • [claimed-docs] “bag: Record/play a rosbag”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Gazebo—none0/10

   No evidence of a versioned API policy or documented deprecation schedule; ROS/Gazebo version compatibility docs mention supporting multiple versions but don't describe an API deprecation policy, and API probes (openapi, llms.txt) all 404. Missing for 10: any explicit versioning/deprecation policy documentation, API changelogs, or stability guarantees for AI/agentic consumers.

   • [claimed-docs] “This document provides guidance on using different versions of ROS in combination with different versions of Gazebo.”
   • [claimed-docs] “This document provides guidance on using different versions of ROS in combination with different versions of Gazebo. We recommend reading it…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://gazebosim.org/llms.txt”

   proof ↗⚑ flag

   ROS 2—none0/10

   No evidence in the pack references API versioning policy, deprecation guidelines, or backward-compatibility guarantees for ROS 2 APIs/interfaces; the docs cover features, tools, and QoS but not a documented deprecation/versioning policy. missing for 10: documented API versioning scheme, formal deprecation policy/timeline, compatibility guarantees across releases.

   ⚑ flag

1. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to ROS 2
   Gazebo—none0/10

   Gazebo's evidence shows a plugin architecture for developers to extend robot/sensor/environment behavior in C++, but there is no documented rule-based trigger-action automation system for AI-native/non-developer users to define event-driven rules declaratively.

   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Develop custom plugins for robot, sensor, and environment control.”
   • [claimed-docs] “Users: For those who primarily run Gazebo using standard tools (like gz sim), edit SDFormat files, use existing plugins, and interact with r…”

   proof ↗⚑ flag

   ROS 2~partialclaimed4/10

   ROS 2's pub/sub, services, and actions model is inherently event-driven — subscribing to a topic or lifecycle event triggers a callback/action, which is a form of automatic reaction to events (ros2-docs-10, ros2-docs-24, ros2-docs-5). However, there is no evidence of a declarative 'rules engine' or AI-native trigger-condition-action system; this capability exists only as a byproduct of general-purpose programming against the pub/sub API, not as a built-in automation-rule feature. Missing for 10: a documented rules/automation-definition interface (e.g. declarative if-event-then-action config), AI-native tooling to define such rules without writing node code, and independent evidence of this pattern being used for automation purposes.

   • [claimed-docs] “Topics: For continuous data streams. Services: For synchronous request/response interactions. Actions: For long-running tasks with feedback”
   • [claimed-docs] “Actions allow clients to send goals, receive feedback during the execution, cancel if needed, and return a result if availabl”
   • [claimed-docs] “Support for nodes with managed lifecycles”
   • [claimed-docs] “Launch system for coordinating multiple nodes”

   proof ↗⚑ flag

Bring up

1. robotics engineerSwap sensors and actuators behind stable hardware-abstraction interfaces without rewriting application code

   weight 3 · round to ROS 2
   Gazebo~partialclaimed5/10

   Gazebo's plugin architecture lets robot, sensor, environment, and physics-engine components be swapped as plugins (gazebo-gh-1/7, gazebo-gh-2, gazebo-docs-15), and simulated hardware is accessed via SDF/gz-transport rather than hard-coded app logic, which supports a hardware-abstraction-like workflow. However, the evidence never explicitly discusses interface stability guarantees or confirms application code is untouched when swapping sensors/actuators. Missing for 10: explicit documentation of stable/versioned sensor-actuator interface contracts, and case evidence that application code needed zero changes across a hardware swap.

   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Dynamics simulation: Access multiple high-performance physics engines through Gazebo Physics.”
   • [claimed-docs] “A plugin based interface to physics engines, such as ODE, Bullet, and DART.”
   • [github] “Simulation models: Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other p…”

   proof ↗⚑ flag

   ROS 2~partialclaimed6/10

   ROS 2's core architecture—standard message packages, topics/services/actions interfaces, and multi-language client libraries—is exactly the mechanism that lets drivers for different sensors/actuators publish/subscribe to the same standardized interface, enabling swap-in-place hardware. However, the evidence pack never explicitly documents a 'hardware abstraction layer' concept, driver ecosystem practices, or a concrete example of swapping a sensor/actuator without app changes. Missing for 10: explicit hardware-abstraction/driver-interface documentation, named sensor/actuator driver packages demonstrating swap-ability, and independent hands-on confirmation that application code needs no changes when hardware is swapped.

   • [claimed-docs] “Topics: For continuous data streams. Services: For synchronous request/response interactions. Actions: For long-running tasks with feedback”
   • [claimed-docs] “The topic interface is meant for continuous data streams, for example, streaming sensor data or the status of your robot.”
   • [claimed-docs] “The service interface is meant for synchronous request/response interactions, for example, when you want to send a query requesting the conf…”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “ROS-Base Install (Bare Bones): Communication libraries, message packages, command line tools. No GUI tools.”
   • [claimed-docs] “client libraries expose to users the core functionality that makes ROS "ROS"”

   proof ↗⚑ flag

2. robotics engineerBring up a new robot — drivers, configuration, first motion — in hours rather than weeks

   weight 3 · round to Gazebo
   Gazebo~partialclaimed5/10

   Gazebo provides reusable robot/sensor plugins, Fuel-hosted models (PR2, TurtleBot, etc.), SDF snippet copy-paste, and CLI tools that could speed up assembling a simulated robot and getting first motion quickly, but there is no first-party or independent evidence of an actual hours-vs-weeks bring-up workflow, driver integration, or hardware configuration case study. missing for 10: quantified bring-up time claims, driver/hardware configuration workflow evidence, independent case study or hands-on report of a new robot going from zero to first motion

   • [github] “Simulation models: Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other p…”
   • [github] “Develop custom plugins for robot, sensor, and environment control.”
   • [claimed-docs] “click on the <> icon in the model description page... to copy an SDF snippet into your clipboard. This snippet can be pasted directly into y…”
   • [github] “Extensive command line tools for increased simulation introspection and control.”
   • [claimed-docs] “Users: For those who primarily run Gazebo using standard tools (like gz sim), edit SDFormat files, use existing plugins, and interact with r…”

   proof ↗⚑ flag

   ROS 2!disputedcontradicted5/10

   ROS 2 docs show strong building blocks for hardware bring-up (launch system for coordinating nodes, CLI tools for introspection/pub-sub, multi-language client libraries, parameters, lifecycle nodes, drivers ecosystem implied by ros2-gh-1) that in principle let an engineer wire up a robot quickly. However, independent hands-on community reports concretely contradict the 'hours not weeks' claim: reports of dependency hell, a convoluted build system, disorganized tutorials causing 'weird errors,' and even advice to budget a full 'Epic: Migrate off of ROS' once shipping — while one commenter admits it's fast only for hobbyist/prototype use, not production bring-up. Missing for 10: a first-party quantified bring-up example (e.g., time-to-first-motion tutorial) and independent corroboration that real hardware bring-up is fast, not just prototyping.

   • [claimed-docs] “Launch system for coordinating multiple nodes”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “ROS 2 includes a suite of command-line tools for introspecting a ROS 2 system.”
   • [github] “The Robot Operating System (ROS) is a set of software libraries and tools that help you build robot applications. From drivers to state-of-t…”
   • [community] “If you are a hobbyist, academic or garage startup, absolutely use ROS. It will take you from nothing to something faster than anything. But,…”
   • [community] “ROS is, in my opinion, dying on the industry front. It is a dependency hell; resource-heavy on embedded systems; too slow for real-time, hig…”
   • [community] “I'd love to use something other than ROS2, if for no other reason than to get rid of the dependency hell and the convoluted build system. Bu…”
   • [community] “I usually feel the same when starting something new... Installing/building ROS, the package boilerplate, etc... But then again I often end u…”
   • [community] “I'm really struggling in learning ROS in a systematic way. The tutorials are all over the place and somehow unorganized IMO. When trying to …”

   proof ↗⚑ flag

Ecosystem modules

1. developerPull reusable packages or modules from a registry or ecosystem for common hardware and behaviors

   weight 1 · round to Gazebo
   Gazebo✓fullclaimed6/10

   Gazebo Fuel is documented as a registry/ecosystem from which developers can pull ready-made robot models (PR2, TurtleBot, etc.) and physically accurate environment models, and the docs show copying SDF snippets directly from a model's Fuel page into a project; plugins extend hardware/behavior reuse further. missing for 10: no evidence of versioning/dependency management, search/discovery tooling details, or independent hands-on corroboration of the Fuel registry experience.

   • [github] “Simulation models: Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other p…”
   • [github] “Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other physically accurate …”
   • [claimed-docs] “click on the <> icon in the model description page... to copy an SDF snippet into your clipboard. This snippet can be pasted directly into y…”
   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Develop custom plugins for robot, sensor, and environment control.”

   proof ↗⚑ flag

   ROS 2~partialcommunity4/10

   Community comments confirm a broad ecosystem of pre-built ROS drivers/nodes exists that developers rely on ('a lot of nodes and drivers out there', 'data bagging, visualization, teleop, and sim... for free'), and docs show packages are distributed via apt-installable debs (Desktop/ROS-Base installs), implying a package ecosystem. However there is no first-party documentation in the pack describing an actual registry/index (e.g. ROS Index, rosdep, ros-<distro>-* apt packages) or concrete examples of pulling hardware-specific packages. Missing for 10: explicit registry/package-manager documentation, examples of installing a specific hardware driver or behavior package, and independent corroboration beyond passing community remarks.

   • [community] “I'd love to use something other than ROS2, if for no other reason than to get rid of the dependency hell and the convoluted build system. Bu…”
   • [community] “I've been a ROS 1 (and now 2) user since 2010... ROS gives you some important things 'for free' if you cooperate with its ecosystem conventi…”
   • [community] “I usually feel the same when starting something new... Installing/building ROS, the package boilerplate, etc... But then again I often end u…”
   • [claimed-docs] “Desktop Install (Recommended): ROS, RViz, demos, tutorials.”
   • [claimed-docs] “ROS-Base Install (Bare Bones): Communication libraries, message packages, command line tools. No GUI tools.”

   proof ↗⚑ flag

Sensors

1. robotics engineerIntegrate cameras, lidars, IMUs, and GPS with ready-made drivers and standard message types

   weight 2 · round drawn
   Gazebo~partialclaimed4/10

   Evidence confirms Gazebo supports sensor/robot plugins generally (gazebo-gh-7) and ROS integration via ros_gz (gazebo-docs-9, gazebo-docs-13, gazebo-docs-18), implying standard message compatibility, but no evidence specifically names ready-made camera, lidar, IMU, or GPS driver plugins or standard message types used. missing for 10: explicit documentation of built-in sensor plugin types (camera/lidar/IMU/GPS), confirmation of standard ROS/Gazebo message schemas for each, and hands-on verification of sensor bring-up.

   • [github] “Develop custom plugins for robot, sensor, and environment control.”
   • [claimed-docs] “This document provides guidance on using different versions of ROS in combination with different versions of Gazebo.”
   • [claimed-docs] “This document provides guidance on using different versions of ROS in combination with different versions of Gazebo. We recommend reading it…”
   • [claimed-docs] “The following command will install the correct version of Gazebo and ros_gz for your ROS installation on a Linux system.”

   proof ↗⚑ flag

   ROS 2~partialcommunity4/10

   Evidence confirms ROS 2 ships standard message packages and a large driver/node ecosystem in general terms (ros2-docs-44 'message packages'; ros2-comm-7 'a lot of nodes and drivers out there for ROS already'; ros2-comm-16 on standardized robotics datatypes), but there is no explicit documentation of specific camera, lidar, IMU, or GPS driver packages or sensor_msgs/standard sensor message types. missing for 10: explicit docs listing camera/lidar/IMU/GPS driver packages, sensor_msgs or NavSat message specifics, first-party hardware integration guides.

   • [claimed-docs] “ROS-Base Install (Bare Bones): Communication libraries, message packages, command line tools. No GUI tools.”
   • [community] “I'd love to use something other than ROS2, if for no other reason than to get rid of the dependency hell and the convoluted build system. Bu…”
   • [community] “ROS is popular because it's like a big collection of .proto or .thrift files for complex robotics datatypes that everyone agrees to use in t…”

   proof ↗⚑ flag

Data

1. developerQuery and export collected robot data through an API or SQL for offline analysis

   weight 2 · round to ROS 2
   Gazebo—none0/10

   No evidence of any SQL database, data export tool, or query API for offline analysis of collected robot/simulation data; evidence only covers transport messaging, plugins, and CLI simulation control, and API probes for OpenAPI/docs endpoints returned 404.

   ⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2 provides rosbag2 with a Python API for reading and writing recorded data (ros2-docs-17, ros2-docs-23) and CLI tools for recording/playing bags (ros2-docs-39), enabling offline analysis of collected data programmatically. However, no evidence documents a SQL query interface or export mechanism, despite rosbag2's known SQLite backend not being mentioned in this pack. Missing for 10: explicit SQL querying/export documentation, examples of offline analysis workflows, and independent corroboration of API usability for this purpose.

   • [claimed-docs] “It also provides a Python API for reading from and writing to a bag from your own source code.”
   • [claimed-docs] “This allows you to subscribe to a topic and save the received data to a bag at the same time as performing any other processing of your choi…”
   • [claimed-docs] “bag: Record/play a rosbag”
   • [claimed-docs] “Topic statistics are built-in measurements that help you understand how messages behave when a subscription receives them.”

   proof ↗⚑ flag

Deploy

1. developerRun automated tests of robot software in CI, including simulation-based regression tests

   weight 2 · round to Gazebo
   Gazebo~partialclaimed4/10

   Gazebo supports headless server-only execution and CLI-driven simulation control, which are prerequisites for CI-based regression testing, but there is no evidence of a documented CI integration, test harness, or automated regression-test framework/examples. missing for 10: CI pipeline examples (e.g. GitHub Actions), automated test/assertion framework for simulation regression, documented headless test workflows, third-party corroboration of CI usage.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “the gz-sim10-server package provides a lightweight alternative. It installs only the Gazebo simulation server (gz-sim-server) without any GU…”
   • [github] “Command line tools: Extensive command line tools for increased simulation introspection and control.”
   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”

   proof ↗⚑ flag

   ROS 2—none0/10

   The evidence pack shows ROS 2 can launch simulations (Gazebo) and record/playback data via rosbag, but contains no documentation or evidence of automated testing frameworks (e.g., colcon test, launch_testing), CI pipeline integration, or simulation-based regression testing workflows. Without concrete evidence of a CI-oriented test harness or regression-testing tooling, the story is unevidenced even though the axis clearly applies to a robotics middleware/deployment story.

   • [claimed-docs] “Launch a Simulation with Gazebo and ROS 2”
   • [claimed-docs] “It also provides a Python API for reading from and writing to a bag from your own source code.”
   • [claimed-docs] “This allows you to subscribe to a topic and save the received data to a bag at the same time as performing any other processing of your choi…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Gazebo~partialclaimed5/10

   Gazebo can run fully headless via the `-s` server flag and exposes CLI tools plus gz-transport for programmatic introspection/control, suggesting most simulation functionality is scriptable outside the GUI. However, there is no explicit documentation claiming full feature parity between the GUI (which is plugin-based and includes visualization-only components) and the API/CLI surface. Missing for 10: an explicit statement or evidence that every GUI capability (especially visualization/plugin-specific GUI features) is exposed via API/CLI, and any third-party confirmation of parity.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “the GUI can be run independently using the -g (gui only) flag. On start, the GUI will attempt to connect to a server instance.”
   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the `-s` (server only) flag.”
   • [github] “Command line tools: Extensive command line tools for increased simulation introspection and control.”
   • [github] “Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [claimed-docs] “A framework for graphical user interfaces centered around QT. Each component in Gazebo GUI is an independent plugin”

   proof ↗⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2's architecture is fundamentally API/CLI-first: docs show that features like bag recording (ros2 bag CLI and equivalent Python API [ros2-docs-17],[ros2-docs-23]), security keystore creation (CLI [ros2-docs-42]), and topic pub/sub ([ros2-docs-9],[ros2-docs-38]) are all backed by client-library APIs, and the CLI tools themselves are described as an 'extensible framework' built on the same graph introspection layer as the daemon ([ros2-docs-30],[ros2-docs-52]). However there is no explicit documentation claiming full parity between GUI tools (e.g., RViz, which is only mentioned as part of the Desktop install [ros2-docs-51]) and the client-library APIs, nor any statement that everything visualizable/configurable in RViz can be replicated purely via API. Missing for 10: explicit API/GUI parity claim, documentation of RViz-equivalent functionality via API, and independent confirmation that AI-native/headless workflows can fully replace GUI-based configuration.

   • [claimed-docs] “ROS 2 includes a suite of command-line tools for introspecting a ROS 2 system.”
   • [claimed-docs] “$ ros2 topic pub /chatter std_msgs/msg/String "data: Hello world"”
   • [claimed-docs] “It also provides a Python API for reading from and writing to a bag from your own source code.”
   • [claimed-docs] “This allows you to subscribe to a topic and save the received data to a bag at the same time as performing any other processing of your choi…”
   • [claimed-docs] “Command-line introspection tools using an extensible framework”
   • [claimed-docs] “The main entry point for the tools is the command ros2, which itself has various sub-commands for introspecting and working with nodes, topi…”
   • [claimed-docs] “ros2 security create_keystore demo_keystore”
   • [claimed-docs] “Desktop Install (Recommended): ROS, RViz, demos, tutorials.”
   • [claimed-docs] “ROS 2 runs a background daemon process that maintains information about the ROS graph to provide faster responses to queries, such as the li…”

   proof ↗⚑ flag

2. ai-native userRead the product's source under an open license

   weight 2 · round to ROS 2
   Gazebo~partialclaimed5/10

   Evidence confirms the source code is publicly hosted on GitHub (github.com/gazebosim/gz-sim) with docs describing internals, implying open availability, but no citation explicitly states an open-source license (e.g., Apache-2.0) or links a LICENSE file. Missing for 10: explicit license text/citation, confirmation of license type, and any independent verification of licensing terms.

   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Graphical interface: Create, introspect and interact with your simulations through plugin-based graphical interfaces powered by Gazebo GUI.”
   • [claimed-docs] “Developers: For those who use individual Gazebo libraries (like gz-math, sdformat, or gz-transport) directly in their own C++ applications, …”

   proof ↗⚑ flag

   ROS 2✓fullclaimed8/10

   ROS 2 is hosted publicly on GitHub (github.com/ros2/ros2) as an open-source project, consistent with its well-known Apache 2.0 licensing, and the docs/source are openly accessible for inspection. Missing for 10: explicit license file citation and independent confirmation of license terms beyond the GitHub repo listing.

   • [github] “The Robot Operating System (ROS) is a set of software libraries and tools that help you build robot applications. From drivers to state-of-t…”

   proof ↗⚑ flag

3. ai-native userSelf-host the core product

   weight 3 · round drawn
   Gazebo✓fullclaimed8/10

   Gazebo is open-source, self-installable software with documented server-only installs (gz-sim10-server package, headless -s flag) and remote TCP/IP transport for running simulation on remote servers, enabling full self-hosting of the core simulation engine. missing for 10: no explicit containerized/docker self-hosting guide or independent third-party confirmation of a full self-hosted deployment at scale.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “the gz-sim10-server package provides a lightweight alternative. It installs only the Gazebo simulation server (gz-sim-server) without any GU…”
   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the `-s` (server only) flag.”
   • [claimed-docs] “It installs only the Gazebo simulation server (`gz-sim-server`) without any GUI or Qt dependencies, resulting in a significantly smaller ins…”
   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”

   proof ↗⚑ flag

   ROS 2✓fullcommunity8/10

   ROS 2 is a fully open-source framework distributed via apt/source with no cloud dependency, installable and run entirely on user-owned infrastructure (ROS-Base and Desktop install options, CLI tools, client libraries). Community evidence confirms it is widely self-hosted in production and research despite operational complaints. missing for 10: no explicit first-party 'self-hosting' guide or containerized deployment reference architecture, and no independent audit confirming zero external calls.

   • [claimed-docs] “ROS-Base Install (Bare Bones): Communication libraries, message packages, command line tools. No GUI tools.”
   • [claimed-docs] “Desktop Install (Recommended): ROS, RViz, demos, tutorials.”
   • [claimed-docs] “The default middleware that ROS 2 uses is `Fast DDS`, but the middleware (RMW) can be replaced at runtime.”
   • [github] “The Robot Operating System (ROS) is a set of software libraries and tools that help you build robot applications. From drivers to state-of-t…”
   • [community] “I've been a ROS 1 (and now 2) user since 2010... ROS gives you some important things 'for free' if you cooperate with its ecosystem conventi…”
   • [community] “I still remember the time before ROS, 20 years ago, when each robotics team had to designate a sub-team just for building and maintaining th…”

   proof ↗⚑ flag

Safety

1. ops leadControl with roles and permissions who is allowed to command, configure, or view each robot

   weight 1 · round to ROS 2
   Gazebo—none0/10

   No evidence of any role-based access control, user permissions, or authentication system in Gazebo; it is a robotics simulator with no mention of RBAC or multi-user access governance.

   ⚑ flag

   ROS 2~partialclaimed4/10

   ROS 2's SROS2 security layer provides per-node 'security enclaves' with DDS-Security authentication and permissions policies that can restrict which participants may publish, subscribe, or call services — a mechanism that could be used to gate who can command/configure/view a robot's topics and services (ros2-docs-12,13,15,29,40,42,49). However, this is a low-level, certificate-based node/participant authorization system, not a role-based access model for human operators (no user/role management UI, no built-in 'ops vs viewer' role concept), and no community evidence corroborates real-world use for this purpose. Missing for 10: explicit human-role/permission management (RBAC for ops users), UI/dashboard for granting per-robot view/command rights, and independent hands-on validation of the security enclave workflow.

   • [claimed-docs] “ROS 2 includes the ability to secure communications among nodes within the ROS 2 computational graph.”
   • [claimed-docs] “A security enclave encapsulates a single policy for protecting ROS communications.”
   • [claimed-docs] “The `sros2` package provides the tools and instructions to use ROS 2 on top of DDS-Security.”
   • [claimed-docs] “DDS-Security support”
   • [claimed-docs] “Built-in ROS 2 security features enable control over communications throughout the ROS graph. This not only allows for encrypting data in tr…”
   • [claimed-docs] “ros2 security create_keystore demo_keystore”
   • [claimed-docs] “Built-in ROS 2 security features enable control over communications throughout the ROS graph. This not only allows for encrypting data in tr…”

   proof ↗⚑ flag

2. robotics engineerImplement emergency-stop and safety-interlock patterns the platform documents and supports

   weight 3 · round to ROS 2
   Gazebo—none0/10

   While Gazebo supports custom plugins for robot/sensor/environment control and command-line introspection tools that could theoretically be used to build safety logic, none of the evidence mentions emergency-stop, safety-interlock, or any documented safety pattern/support specifically. missing for 10: any documentation or example referencing e-stop or safety-interlock patterns, guidance on implementing safety-critical control logic, or built-in safety plugin APIs.

   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Extensive command line tools for increased simulation introspection and control.”
   • [claimed-docs] “Developers: For those who use individual Gazebo libraries (like gz-math, sdformat, or gz-transport) directly in their own C++ applications, …”

   proof ↗⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2 documents managed lifecycle nodes (ros2-docs-5), which are the standard building block for implementing safety-interlock/state-transition patterns like emergency stop, plus QoS tuning (ros2-docs-14/22/41) and preliminary real-time support (ros2-docs-32) that engineers rely on for safety-critical control loops. However, there is no explicit documented emergency-stop tutorial, reference pattern, or safety-certification guidance in the evidence. Missing for 10: dedicated emergency-stop/safety-interlock tutorial or design guide, explicit safety-certification or functional-safety documentation, and independent confirmation that lifecycle nodes are used successfully for e-stop in production.

   • [claimed-docs] “Support for nodes with managed lifecycles”
   • [claimed-docs] “ROS 2 can be as reliable as TCP or as best-effort as UDP, with many, many possible states in between.”
   • [claimed-docs] “ROS 2 offers a rich variety of Quality of Service (QoS) policies that allow you to tune communication between nodes.”
   • [claimed-docs] “Preliminary support for real-time code”
   • [claimed-docs] “ROS 2 can be as reliable as TCP or as best-effort as UDP, with many, many possible states in between”

   proof ↗⚑ flag

Sdk agentic

1. ai-native userHave an AI agent authenticate with scoped credentials and command a real robot end-to-end through the platform's API or SDK

   weight 3 · round to ROS 2
   Gazebo—none0/10

   Evidence describes Gazebo as a physics simulator with C++/plugin APIs, transport messaging, and CLI tools for simulated robots, but there is no mention of authentication, scoped credentials, or any mechanism for an AI agent to command a real (non-simulated) robot end-to-end via an API/SDK. Probes for API/auth surfaces (llms.txt, openapi.json) also returned 404s.

   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Simulation models: Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other p…”
   • [github] “Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other physically accurate …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://gazebosim.org/openapi.json, https://gazebosim.org/swagger.json, https://gazebosim.org/api/op…”

   proof ↗⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2 provides DDS-Security with per-node 'security enclaves' encapsulating a single policy (scoped permissions) plus keystore/authentication tooling (ros2-docs-12,13,15,40,42,49), and its client libraries (rclcpp/rclpy) plus topics/services/actions let a program (including an AI agent) command a robot end-to-end via a real API/SDK (ros2-docs-7,10,24,35,36). However, there is no documentation of an AI-agent-oriented credential model (e.g., token/OAuth-style scoped API keys), no explicit workflow for an agent authenticating and issuing end-to-end commands, and no independent evidence of this being used by AI agents in practice. missing for 10: agent-specific scoped credential/token issuance workflow, explicit AI-agent authentication example, independent/hands-on validation of an agent driving a real robot end-to-end via this security model.

   • [claimed-docs] “ROS 2 includes the ability to secure communications among nodes within the ROS 2 computational graph.”
   • [claimed-docs] “A security enclave encapsulates a single policy for protecting ROS communications.”
   • [claimed-docs] “The `sros2` package provides the tools and instructions to use ROS 2 on top of DDS-Security.”
   • [claimed-docs] “Built-in ROS 2 security features enable control over communications throughout the ROS graph. This not only allows for encrypting data in tr…”
   • [claimed-docs] “ros2 security create_keystore demo_keystore”
   • [claimed-docs] “Built-in ROS 2 security features enable control over communications throughout the ROS graph. This not only allows for encrypting data in tr…”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “Topics: For continuous data streams. Services: For synchronous request/response interactions. Actions: For long-running tasks with feedback”
   • [claimed-docs] “Actions allow clients to send goals, receive feedback during the execution, cancel if needed, and return a result if availabl”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “client libraries expose to users the core functionality that makes ROS "ROS"”

   proof ↗⚑ flag

2. ai-native userIntegrate vision-language-action or robotics foundation models into my robot's autonomy stack through supported tooling

   weight 2 · round drawn
   Gazebo—none0/10

   Evidence covers Gazebo's general plugin architecture, transport, physics engines, and ROS integration, but there is no mention of VLA models, robotics foundation models, or any supported tooling/SDK for integrating such models into an autonomy stack. Nothing in the pack ties Gazebo to AI/foundation-model integration workflows.

   ⚑ flag

   ROS 2—none0/10

   The evidence pack covers ROS 2's core middleware, client libraries, CLI tools, QoS, security, and simulation features, but contains no mention of VLA models, robotics foundation models, or any supported tooling/integration path (e.g., official packages, tutorials, or SDKs) for incorporating such AI models into the autonomy stack. Missing for 10: any documentation or examples of VLA/foundation-model integration, official model-serving nodes, or partner tooling (e.g., NVIDIA Isaac, Hugging Face robotics integrations) referenced by ROS 2 itself.

   ⚑ flag

Sdks

1. developerBuild against official, typed SDKs in multiple languages (Python, TypeScript, Go, C++) that cover the platform's full surface

   weight 3 · round to ROS 2
   Gazebo—none0/10

   Evidence shows Gazebo is primarily a C++ library/simulator with plugin APIs, ROS integration, and CLI tools, but there is no mention of official typed SDKs in Python, TypeScript, or Go, nor any unified multi-language SDK covering the platform surface. Missing for 10: Python/TypeScript/Go SDK docs, typed client libraries, and evidence of full API-surface coverage across languages.

   • [claimed-docs] “Developers: For those who use individual Gazebo libraries (like gz-math, sdformat, or gz-transport) directly in their own C++ applications, …”
   • [claimed-docs] “If your package directly depends on a Gazebo library, instead of relying only on ros_gz, refer to this documentation to learn how to use the…”
   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”

   proof ↗⚑ flag

   ROS 2~partialclaimed5/10

   ROS 2 docs confirm official client libraries in multiple languages, but only explicitly evidence C++ and Python (rclcpp/rclpy) as officially verified APIs, with no mention of official TypeScript or Go SDKs covering the full ROS 2 surface (nodes, topics, services, actions, QoS, security, etc.). Community remarks confirm long-standing use of C++/Python but do not corroborate TypeScript/Go as first-party. Missing for 10: official TypeScript SDK, official Go SDK, evidence that all four languages have full-surface parity and 'typed' guarantees.

   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “This verifies both the C++ and Python APIs are working properly.”
   • [claimed-docs] “you might prefer to write visualization tools in Python because it makes prototyping iterations faster, while for parts of your system that …”
   • [claimed-docs] “Client libraries come in a variety of programming languages so that users may write ROS 2 code in the language that is best-suited for their…”
   • [claimed-docs] “client libraries expose to users the core functionality that makes ROS "ROS"”

   proof ↗⚑ flag

Sim

1. robotics engineerSimulate my robot and its environment with realistic physics and sensor models before touching hardware

   weight 3 · round to Gazebo
   Gazebo✓fullclaimed7/10

   Gazebo's core purpose is physics-and-sensor simulation: docs/GitHub evidence confirms multiple physics engines (ODE, Bullet, DART), plugin-based sensor and robot control, access to physically accurate robot/environment models via Fuel, and SDF-based world/robot description before hardware deployment. Missing for 10: independent/hands-on validation of sensor model realism (e.g. lidar/camera noise fidelity) and no third-party benchmark or case study corroborating physics accuracy claims beyond vendor docs.

   • [github] “Dynamics simulation: Access multiple high-performance physics engines through Gazebo Physics.”
   • [claimed-docs] “A plugin based interface to physics engines, such as ODE, Bullet, and DART.”
   • [github] “Plugins: Develop custom plugins for robot, sensor, and environment control.”
   • [github] “Simulation models: Access numerous robots including PR2, Pioneer2 DX, iRobot Create, and TurtleBot, and construct environments using other p…”
   • [github] “Graphical interface: Create, introspect and interact with your simulations through plugin-based graphical interfaces powered by Gazebo GUI.”
   • [claimed-docs] “click on the <> icon in the model description page... to copy an SDF snippet into your clipboard. This snippet can be pasted directly into y…”

   proof ↗⚑ flag

   ROS 2~partialclaimed3/10

   ROS 2 docs reference a tutorial for launching a Gazebo simulation with ROS 2, indicating an integration path exists, but there is no detail on physics fidelity, sensor model realism, or independent corroboration of simulation quality. missing for 10: documentation of physics engine accuracy, sensor plugin catalog (cameras, lidar, IMU), community/hands-on validation of sim-to-real fidelity.

   • [claimed-docs] “Launch a Simulation with Gazebo and ROS 2”

   proof ↗⚑ flag

2. robotics engineerRun the same robot code against simulation and the real robot without a rewrite

   weight 2 · round to ROS 2
   Gazebo~partialclaimed5/10

   Gazebo's plugin/transport architecture and ROS integration (ros_gz, TCP/IP transport, command-line/introspection tools) suggest that robot control code communicating via standard ROS topics/services could target both simulated and real robots, but no evidence explicitly describes a sim-to-real code-reuse workflow or hardware-in-the-loop testing. missing for 10: explicit documentation or case study of running identical control code against simulated and physical robots, no independent corroboration of a no-rewrite workflow.

   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [claimed-docs] “If your package directly depends on a Gazebo library, instead of relying only on ros_gz, refer to this documentation to learn how to use the…”
   • [claimed-docs] “This document provides guidance on using different versions of ROS in combination with different versions of Gazebo.”
   • [github] “Develop custom plugins for robot, sensor, and environment control.”

   proof ↗⚑ flag

   ROS 2✓fullcommunity7/10

   ROS 2's architecture (topics/services/actions abstraction, pub/sub) lets nodes interact with either real hardware drivers or simulated ones (e.g., Gazebo) using the identical ROS API, and the docs explicitly walk through launching a Gazebo simulation alongside ROS 2 nodes, plus a community user notes ROS gives you sim 'for free' as part of its ecosystem. Missing for 10: an explicit vendor statement that the same node code requires zero changes to move from sim to real robot, and independent hands-on corroboration/case study confirming no-rewrite in practice.

   • [claimed-docs] “Launch a Simulation with Gazebo and ROS 2”
   • [claimed-docs] “Publish/subscribe over topics”
   • [claimed-docs] “Topics: For continuous data streams. Services: For synchronous request/response interactions. Actions: For long-running tasks with feedback”
   • [claimed-docs] “Inter- and intra-process communication using the same API”
   • [community] “I've been a ROS 1 (and now 2) user since 2010... ROS gives you some important things 'for free' if you cooperate with its ecosystem conventi…”

   proof ↗⚑ flag

Sim training

1. developerGenerate synthetic training data and run reinforcement learning at scale in simulation

   weight 2 · round to Gazebo
   Gazebo~partialclaimed5/10

   Gazebo provides infrastructure that supports large-scale simulation runs: headless server-only mode, a lightweight server-only package, TCP/IP transport for remote servers, and CLI tools for introspection/control, which together enable running many simulation instances programmatically. However, there is no direct evidence of built-in synthetic data generation pipelines, RL training integrations, or scaling/orchestration tooling specifically for RL workflows. Missing for 10: explicit RL framework integration (e.g. gym-style APIs), documented synthetic dataset export tooling, and evidence of distributed/parallel scaling for training at scale.

   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “the gz-sim10-server package provides a lightweight alternative. It installs only the Gazebo simulation server (gz-sim-server) without any GU…”
   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Extensive command line tools for increased simulation introspection and control.”
   • [claimed-docs] “It installs only the Gazebo simulation server (`gz-sim-server`) without any GUI or Qt dependencies, resulting in a significantly smaller ins…”

   proof ↗⚑ flag

   ROS 2—none0/10

   Evidence shows only a basic Gazebo simulation launch tutorial (ros2-docs-16); there is no mention of synthetic training data generation, reinforcement learning frameworks, or scaled RL training pipelines integrated with ROS 2. The axis is plausible for a robotics middleware (simulation is core to ROS use cases), but no evidence supports the specific RL/synthetic-data-at-scale capability. Missing for 10: RL framework integration (e.g., Isaac Gym/Gazebo RL bridges), synthetic data generation tooling, evidence of scaled/parallel simulation training.

   • [claimed-docs] “Launch a Simulation with Gazebo and ROS 2”

   proof ↗⚑ flag

Teleop

1. robotics engineerInspect live topics, logs, and state on a deployed robot remotely to debug issues

   weight 2 · round to ROS 2
   Gazebo~partialclaimed5/10

   Gazebo provides remote TCP/IP transport (gz-transport) for interfacing with simulations over the network, a headless server mode, and extensive CLI tools for 'simulation introspection and control', which could plausibly extend to inspecting topics/state on a running (simulated or transport-connected) robot. However, none of the evidence explicitly addresses inspecting logs or state on a physically deployed robot, or dedicated remote debugging/monitoring dashboards. Missing for 10: log inspection tooling, explicit remote/robot (non-simulated) debugging workflow, and independent hands-on confirmation of remote monitoring in production robot deployments.

   • [github] “TCP/IP Transport: Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Run simulation on remote servers and interface to Gazebo Sim through socket-based message passing using Gazebo Transport.”
   • [github] “Extensive command line tools for increased simulation introspection and control.”
   • [github] “Command line tools: Extensive command line tools for increased simulation introspection and control.”
   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the -s (server only) flag.”
   • [claimed-docs] “Gazebo Sim can also be run headless, i.e. without the GUI, by using the `-s` (server only) flag.”
   • [github] “Graphical interface: Create, introspect and interact with your simulations through plugin-based graphical interfaces powered by Gazebo GUI.”

   proof ↗⚑ flag

   ROS 2✓fullcommunity8/10

   ROS 2 provides a comprehensive suite of CLI introspection tools (ros2 topic, ros2 node, ros2 service, ros2 bag) plus a daemon for graph state, topic statistics, service introspection, and rosbag recording/playback for logs, all of which support remote debugging of live topics and state on deployed robots. This is corroborated by direct docs on command-line tools, topic statistics, and bag recording, and community comments confirm CLI tools/bags/viewers are valued 'for free' benefits of using ROS's ecosystem conventions. Missing for 10: explicit first-party or independent evidence of remote/networked debugging over real deployments (e.g., cross-machine domain setup docs) and no hands-on account specifically describing remote robot debugging via these tools.

   • [claimed-docs] “ROS 2 includes a suite of command-line tools for introspecting a ROS 2 system.”
   • [claimed-docs] “Command-line introspection tools using an extensible framework”
   • [claimed-docs] “The main entry point for the tools is the command ros2, which itself has various sub-commands for introspecting and working with nodes, topi…”
   • [claimed-docs] “ROS 2 runs a background daemon process that maintains information about the ROS graph to provide faster responses to queries, such as the li…”
   • [claimed-docs] “Topic statistics are built-in measurements that help you understand how messages behave when a subscription receives them.”
   • [claimed-docs] “It also provides a Python API for reading from and writing to a bag from your own source code.”
   • [claimed-docs] “This allows you to subscribe to a topic and save the received data to a bag at the same time as performing any other processing of your choi…”
   • [claimed-docs] “bag: Record/play a rosbag”
   • [claimed-docs] “Service Introspection”
   • [community] “I've been a ROS 1 (and now 2) user since 2010... ROS gives you some important things 'for free' if you cooperate with its ecosystem conventi…”
   • [community] “I usually feel the same when starting something new... Installing/building ROS, the package boilerplate, etc... But then again I often end u…”

   proof ↗⚑ flag