Formant vs ROS 2

Agent access

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

   weight 2 · round to Formant
   Formant✓fullprobed9/10

   A direct probe confirms llms.txt is live and returns a 200 with structured docs content at docs.formant.io/llms.txt, directly satisfying the story. Missing for 10: no independent third-party confirmation of agent usage or broader agent-oriented doc structure beyond the single llms.txt file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.formant.io/llms.txt # Formant Documentation > The Formant software platform allows companies to ru…”

   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 drawn
   Formant~partialclaimed5/10

   Formant provides a Dockerized agent, Python Cloud SDK, Admin API, and webhooks that enable programmatic, non-UI interaction with telemetry, commands, and data ingestion — all of which could be scripted for automated/headless workflows. However, there is no explicit documentation or example of running Formant in a CI pipeline or fully headless automation context; most emphasis is on operator dashboards, teleoperation, and fleet visualization UI. missing for 10: explicit CI/CD integration examples, documented headless mode or automation pipeline guide, evidence of non-interactive/scripted end-to-end workflows.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “A webhook allows you to make an API call to any endpoint over HTTP based on a trigger from a Formant event.”

   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
   Formant—none0/10

   Formant is a robot fleet management platform, not itself an AI agent, so a fair question exists about whether it exposes an official MCP server for agentic access; no evidence pack item mentions MCP at all, only SDKs, REST/webhooks, and Admin API.

   ⚑ 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
   Formant—none0/10

   Evidence shows Formant offers Python Cloud SDK, Agent SDK, RealtimeSDK/toolkit, and REST/Admin APIs, but no documentation or GitHub repo describes an official command-line interface tool.

   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”

   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 Formant
   Formant✓fullprobed8/10

   Formant documents multiple public APIs/SDKs (Agent SDK, Cloud SDK, Admin API, Realtime SDK/toolkit, ingestion API, webhooks) that let developers ingest telemetry, send commands, teleoperate, and build custom apps, with GitHub toolkit repos for hands-on integration. Missing for 10: a discoverable formal OpenAPI/Swagger spec (probe found only 404s) and independent third-party corroboration of API robustness.

   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “A webhook allows you to make an API call to any endpoint over HTTP based on a trigger from a Formant event.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   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 userIssue scoped/least-privilege API credentials for an agent

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

   No evidence of scoped or least-privilege API credential issuance for agents; Formant docs describe agent SDK, admin API, and commands but nothing about API key scoping, permission levels, or credential minimization. Missing for 10: any documentation of scoped/least-privilege API keys, role-based credential issuance, or agent-specific token permissions.

   ⚑ flag

   ROS 2~partialclaimed4/10

   ROS 2's security framework (sros2/DDS-Security) lets you create a keystore and define per-participant 'security enclaves' that encapsulate a distinct authentication/authorization policy, which maps loosely onto the idea of scoped, least-privilege credentials issued to individual nodes/agents. However this is a general robotics middleware security feature, not an API-credential system designed for AI agents, and there's no documented workflow for dynamically issuing/revoking scoped tokens to an 'agent' persona. Missing for 10: agent-oriented credential issuance workflow, dynamic/temporary scoped tokens, any AI-agent-specific access control examples, and independent evidence of least-privilege enforcement in practice.

   • [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”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Formant✓fullprobed7/10

   Formant documents multiple official SDKs — the Agent SDK (telemetry, commands, teleop), the Cloud SDK (Python) for data ingestion/query, and a public GitHub 'toolkit' repo exposing RealtimeSDK and APIs for building custom apps — giving AI-native developers concrete, first-party libraries to build against. Missing for 10: independent/hands-on developer corroboration beyond vendor docs, and a working OpenAPI/swagger spec (probe shows all candidate OpenAPI endpoints 404), which weakens confidence in full API-contract completeness.

   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your device, and more”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [github] “Create realtime visualizations of your robots”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   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 userSet up automations that run autonomously in the background

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

   Formant provides trigger-based automation (webhooks fired from events, automated commands, and fleet orchestration that dispatches robots/help based on operational anomalies), which can run without a human polling the system — a basic form of background automation. However, this is rule/event-based orchestration rather than a documented framework for autonomous, AI-driven background agents, and there's no evidence of scheduling, persistent agent loops, or independent corroboration of unattended operation. Missing for 10: explicit AI-agent-style background automation framework, scheduling/looping capability, and third-party validation of autonomous operation.

   • [claimed-docs] “A webhook allows you to make an API call to any endpoint over HTTP based on a trigger from a Formant event.”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our r…”
   • [claimed-docs] “Build better human-to-robot ratios by automating incident response and creating workflows for monitoring devices at scale.”
   • [claimed-docs] “Assigns the right job to the right robot — regardless of who built it — using operational history and live data, and dispatches help the mom…”
   • [claimed-docs] “Heterogeneous Fleet Orchestration assigns the right job to the right robot — regardless of who built it — using operational history and live…”
   • [claimed-docs] “Get instant visibility into every robot in your fleet. Set up alerts for anomalies, track mission progress, and respond to issues before the…”

   proof ↗⚑ flag

   ROS 2~partialclaimed6/10

   ROS 2 provides the core building blocks for autonomous background execution — a launch system to coordinate multiple nodes, managed node lifecycles, a background daemon process maintaining graph state, and actions for long-running tasks with feedback/cancellation — which together let a robotics system run continuously and autonomously once configured. However, this is generic robotics middleware automation, not anything framed around AI-agent-triggered or AI-native workflow automation specifically. Missing for 10: explicit support for AI-driven/agentic triggering or scheduling of automations, independent hands-on evidence of long-running unattended deployments succeeding, and any AI-specific orchestration tooling.

   • [claimed-docs] “Launch system for coordinating multiple nodes”
   • [claimed-docs] “Support for nodes with managed lifecycles”
   • [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] “Actions allow clients to send goals, receive feedback during the execution, cancel if needed, and return a result if availabl”
   • [claimed-docs] “Multiple executors (at level of callback groups) in same node”

   proof ↗⚑ flag

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

   weight 2 · round to Formant
   Formant~partialclaimed5/10

   Formant's marketing pages mention asking the fleet 'what's happening in plain language' and getting ML-driven task recommendations, plus an 'AI assistant' for building dashboards, indicating some natural-language interaction capability. However, this is only surfaced in marketing copy, not backed by technical documentation, examples, or independent verification, and the bulk of the 'commands' documentation describes predefined/scripted actions rather than open natural-language control. Missing for 10: technical docs on the NL interface, example commands/queries, independent hands-on verification, and clarity on scope of natural-language coverage versus predefined commands.

   • [claimed-docs] “Ask your fleet what's happening in plain language and get governed, ML-driven task recommendations — with people approving what happens next…”
   • [claimed-docs] “Ask your fleet what’s happening in plain language and get governed, ML-driven task recommendations — with people approving what happens next…”
   • [claimed-docs] “Using built-in visualizations, custom SQL queries, or our AI assistant, you can build a rich dashboard for your devices.”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice. Using built-in vis…”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our r…”

   proof ↗⚑ 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
   Formant—none0/10

   Evidence shows documentation and SDK references but no interactive API reference with runnable examples; a probe explicitly found no OpenAPI/swagger spec (404s across candidate paths), and no mention of a try-it-now console or code sandbox.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   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
   Formant—none0/10

   Formant references an Admin API, Cloud SDK, and query API, but a direct probe for OpenAPI/Swagger specs at common paths returned 404 for all candidates, and no evidence pack item links to a downloadable machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”

   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 ROS 2
   Formant—none0/10

   No evidence of a sandbox/staging environment, test devices, or any mechanism to isolate testing from production robot fleets and data; Formant's docs focus on production device management, telemetry, teleoperation, and analytics with no mention of sandboxing.

   ⚑ 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
   Formant—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; probes for an OpenAPI spec all returned 404, and none of the docs mention version numbers or deprecation timelines.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   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 userPerform bulk operations across many items at once

   weight 2 · round to Formant
   Formant~partialclaimed5/10

   Formant offers fleet-wide monitoring, orchestration that assigns jobs across many robots, and a single view to manage multiple fleets simultaneously, plus a programmatic Admin API/Agent SDK that could be scripted to issue commands to many devices at once. However, there is no explicit documentation of a dedicated bulk-operation API or UI (e.g., select-many-and-apply-action) for arbitrary bulk actions across devices. Missing for 10: explicit bulk-command/bulk-update API or UI documentation, evidence of batch processing limits/throughput, and independent confirmation of bulk workflows in practice.

   • [claimed-docs] “Tracks historical performance per robot, per mission — speed, error rates, how a given unit has handled a given job before — alongside curre…”
   • [claimed-docs] “Assigns the right job to the right robot — regardless of who built it — using operational history and live data, and dispatches help the mom…”
   • [claimed-docs] “One view across every vendor's fleet — AMRs, quadrupeds, humanoids, arms — without a separate dashboard, update cycle, or incident format pe…”
   • [claimed-docs] “Manage multiple fleets simultaneously from a single operator view”
   • [claimed-docs] “Build better human-to-robot ratios by automating incident response and creating workflows for monitoring devices at scale.”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our r…”

   proof ↗⚑ flag

   ROS 2~partialclaimed3/10

   ROS 2's launch system lets you coordinate and start many nodes at once, and its CLI/introspection framework can operate across the whole graph (nodes, topics, services), which gives a loose analog to bulk operations, but there's no dedicated batch/bulk API (e.g., batch topic remap, bulk parameter set across nodes, mass import/export) described in the docs. Missing for 10: explicit bulk/batch operation tooling (e.g., scripted mass parameter updates, bulk topic/service operations), any evidence of an AI-native workflow performing such operations, and independent confirmation of this use case.

   • [claimed-docs] “Launch system for coordinating multiple nodes”
   • [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] “Set/retrieve parameters”

   proof ↗⚑ flag

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

   weight 3 · round to Formant
   Formant~partialclaimed6/10

   Formant docs describe event-triggered webhooks ("make an API call to any endpoint over HTTP based on a trigger from a Formant event") and automated incident-response/alerting for anomalies, which directly support rule-based automatic actions on events. However, there's no detailed documentation of a full rules/condition-builder UI, complex logic composition, or independent corroboration of this feature working at scale. Missing for 10: detailed rule-definition interface/logic docs, independent/hands-on validation, examples of multi-condition or chained automations.

   • [claimed-docs] “A webhook allows you to make an API call to any endpoint over HTTP based on a trigger from a Formant event.”
   • [claimed-docs] “Build better human-to-robot ratios by automating incident response and creating workflows for monitoring devices at scale.”
   • [claimed-docs] “Get instant visibility into every robot in your fleet. Set up alerts for anomalies, track mission progress, and respond to issues before the…”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our 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
   Formant~partialclaimed3/10

   Formant advertises connecting to 'multiple robot types with minimal lift' with uniform, searchable data ingestion, and unifying different manufacturers' hardware (AMRs, quadrupeds, arms) into one dashboard/data model, which is a coarse form of hardware abstraction at the fleet-telemetry/command level. However, this is about fleet monitoring and teleop integration, not a documented hardware-abstraction API layer that lets a robotics engineer's application code swap out individual sensors/actuators without code changes — there is no driver-interface or HAL SDK evidence for this. Missing for 10: a documented sensor/actuator driver abstraction layer, evidence of swapping specific hardware components without app-code changes, and independent/hands-on confirmation of this working across heterogeneous hardware.

   • [claimed-docs] “Easily connect to multiple robot types with minimal lift. Ensure all data ingested is uniform and searchable.”
   • [claimed-docs] “One view across every vendor's fleet — AMRs, quadrupeds, humanoids, arms — without a separate dashboard, update cycle, or incident format pe…”
   • [claimed-docs] “a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your device, and more”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”

   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 Formant
   Formant~partialclaimed5/10

   Formant provides quick agent installation (Docker/ROS2), an SDK for telemetry/commands, and low-latency teleoperation that can get a robot reporting data and driving within a short setup window, which speaks to fast bring-up of the software/fleet layer. However, it doesn't provide actual robot driver development or low-level hardware integration — it assumes drivers already exist and layers fleet ops on top — and there's no explicit 'hours not weeks' benchmark or case study demonstrating time-to-first-motion. missing for 10: evidence of driver creation/hardware integration tooling, a concrete time-to-bring-up case study or benchmark, first-motion/actuation examples beyond teleop.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “Easily connect to multiple robot types with minimal lift. Ensure all data ingested is uniform and searchable.”
   • [claimed-docs] “Control robot devices from anywhere over a low-latency, peer-to-peer connection, via joystick and buttons.”
   • [claimed-docs] “Formant's teleoperation provides a secure peer-to-peer connection that enables operators to control any aspect of a system.”

   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 ROS 2
   Formant—none0/10

   Formant provides SDKs, agent installation, and custom module/view building, but there is no evidence of a registry or marketplace of reusable packages for common hardware/behaviors that developers can pull from — modules are custom-built per app rather than shared/discoverable community assets.

   ⚑ 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 to ROS 2
   Formant~partialclaimed3/10

   Formant's docs show a ROS 2 agent install path and a generic Agent/Cloud SDK for ingesting telemetry, plus multi-robot-type connectivity claims, which implies some level of standard-message ingestion (e.g., via ROS topics) but never explicitly names ready-made drivers or standard message types for cameras, lidars, IMUs, or GPS. Missing for 10: explicit driver/adapter documentation per sensor type (camera, lidar, IMU, GPS), confirmation of standard message-type support (e.g., sensor_msgs), and any hands-on evidence of plug-and-play sensor bring-up.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “Easily connect to multiple robot types with minimal lift. Ensure all data ingested is uniform and searchable.”
   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”

   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. developerCapture sensor and telemetry data on-robot and sync it to the cloud with bandwidth-aware policies

   weight 3 · round to Formant
   Formant✓fullclaimed7/10

   Formant's on-robot agent (Docker install, Agent SDK) captures telemetry and sensor data and syncs it to the cloud via the ingestion/query APIs (formant-docs-1, formant-docs-2, formant-docs-3, formant-docs-27), and each data stream can be rate-limited to control bandwidth usage (formant-docs-31), directly supporting bandwidth-aware policies. missing for 10: explicit documentation of offline buffering/store-and-forward behavior during connectivity loss, and independent/hands-on validation of bandwidth policy effectiveness beyond vendor docs.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “Each data stream can be rate-limited, so you don't need to ingest data at high resolution if you don't need it.”

   proof ↗⚑ flag

   ROS 2~partialclaimed3/10

   ROS 2 provides strong on-robot data capture via rosbag (record/play, Python API for custom recording) and configurable QoS policies for tuning network reliability, but there is no evidence of any built-in cloud-sync mechanism or bandwidth-aware upload policy — bags are local artifacts and QoS applies to live DDS pub/sub between nodes, not to offloading recorded data to a cloud backend. Missing for 10: cloud upload/sync capability, bandwidth-aware transfer policies, any first-party cloud integration or partner tooling for telemetry sync.

   • [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] “ROS 2 offers a rich variety of Quality of Service (QoS) policies that allow you to tune communication between nodes.”
   • [claimed-docs] “With the right set of Quality of Service policies, ROS 2 can be as reliable as TCP or as best-effort as UDP, with many, many possible states…”

   proof ↗⚑ flag

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

   weight 2 · round to Formant
   Formant✓fullprobed8/10

   Formant provides a Cloud SDK/query API for pulling telemetry data for offline analysis (formant-docs-3, formant-docs-27) and Analytics with custom SQL queries for aggregating/analyzing device data over time (formant-docs-7, formant-docs-25, formant-docs-16). Missing for 10: a documented OpenAPI/swagger spec (probe found 404s) and independent third-party corroboration of the export workflow beyond first-party docs.

   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “Using built-in visualizations, custom SQL queries, or our AI assistant, you can build a rich dashboard for your devices.”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice. Using built-in vis…”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   proof ↗⚑ 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

Data ml

1. developerFeed collected robot data into model training and deploy the improved model back to the fleet

   weight 2 · round to Formant
   Formant~partialclaimed4/10

   Formant provides data export via the Cloud SDK for querying/collecting telemetry (formant-docs-3, formant-docs-27) and a commands mechanism that can trigger scripts or actions on robots (formant-docs-4, formant-docs-9, formant-docs-29), which could theoretically be used to push a retrained model or trigger redeployment. However, there is no explicit documentation of a model-training integration or a dedicated 'deploy model to fleet' feature — the closest is generic 'AI assistant' and 'ML-driven task recommendations' language which is not about custom model training/deployment. Missing for 10: explicit model training pipeline integration, a documented model artifact deployment/update mechanism, and evidence of round-tripping trained models back onto devices.

   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our r…”
   • [claimed-docs] “We can send commands with the click of a button from the Observe view, or during teleoperation.”
   • [claimed-docs] “Ask your fleet what's happening in plain language and get governed, ML-driven task recommendations — with people approving what happens next…”

   proof ↗⚑ flag

   ROS 2~partialclaimed3/10

   ROS 2 provides rosbag recording/playback (ros2-docs-17, ros2-docs-23) which supports collecting robot data for later use, but there is no evidence of any built-in or documented pathway for feeding that data into model training or deploying updated models back to a robot fleet. missing for 10: model-training integration, fleet-wide model deployment/update mechanism, MLOps tooling, and any end-to-end example connecting bag data to a training loop and redeployment.

   • [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

Fleet

1. ops leadGet alerts on robot faults, battery, and connectivity so issues are caught before customers notice

   weight 2 · round to Formant
   Formant~partialclaimed6/10

   Formant supports alerting-related capabilities: 'Set up alerts for anomalies... respond to issues before they become downtime' and webhook triggers from events, plus fleet-wide visibility and analytics dashboards that could surface battery/connectivity/fault data. However, there's no explicit documentation naming battery level, connectivity loss, or fault-code alerting specifically, nor detail on notification channels (email/SMS/Slack) or configurable thresholds. missing for 10: explicit mention of battery/connectivity/fault-specific alert types, notification channel/escalation details, independent/hands-on confirmation of alerting reliability.

   • [claimed-docs] “Get instant visibility into every robot in your fleet. Set up alerts for anomalies, track mission progress, and respond to issues before the…”
   • [claimed-docs] “A webhook allows you to make an API call to any endpoint over HTTP based on a trigger from a Formant event.”
   • [claimed-docs] “Build better human-to-robot ratios by automating incident response and creating workflows for monitoring devices at scale.”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice. Using built-in vis…”

   proof ↗⚑ flag

   ROS 2—none0/10

   ROS 2 docs describe core middleware capabilities (topics, services, QoS, security, CLI introspection, bag recording) but there is no evidence of any built-in alerting, notification, or ops-dashboard system that would notify an ops lead about robot faults, battery levels, or connectivity issues proactively. Diagnostics-like data could theoretically be built on top of topics, but no such alerting feature or fleet-ops tooling is documented.

   ⚑ flag

2. ops leadPush configuration changes across many robots at once with per-group targeting

   weight 2 · round to Formant
   Formant~partialclaimed5/10

   Formant supports device configuration (formant-docs-14/26), custom commands via Admin API (formant-docs-4/9), and multi-device 'coherence group views' (formant-gh-2) plus managing multiple fleets from one view (formant-docs-22), suggesting some grouped/bulk operational capability. However there is no explicit documentation of pushing configuration changes in bulk with per-group targeting as a named feature. Missing for 10: explicit bulk config-push workflow, documented per-group targeting UI/API, and independent confirmation of at-scale config rollout.

   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our r…”
   • [claimed-docs] “configure devices, design custom views and modules, and build a backend for your custom application.”
   • [claimed-docs] “configure devices, design custom views and modules, and build a backend for your custom application”
   • [github] “Modules can now work with multiple devices in coherence group views”
   • [claimed-docs] “Manage multiple fleets simultaneously from a single operator view”

   proof ↗⚑ flag

   ROS 2—none0/10

   ROS 2's documented features cover per-node parameters, launch systems for coordinating multiple nodes on one robot, and CLI introspection tools, but there is no evidence of a fleet-wide configuration push mechanism with per-group targeting across many robots — that is a higher-level fleet-management capability (e.g., separate tools like open-rmf) not shown here.

   • [claimed-docs] “Launch system for coordinating multiple nodes”
   • [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…”

   proof ↗⚑ flag

3. ops leadMonitor the health, location, and status of a whole robot fleet from one dashboard

   weight 3 · round to Formant
   Formant✓fullclaimed9/10

   Formant's documentation and marketing explicitly describe fleet-wide visibility ('instant visibility into every robot in your fleet', 'current location and status', unified dashboard across vendors, anomaly alerts), directly matching the ops-lead story of monitoring health, location, and status from one dashboard. Missing for 10: independent/hands-on third-party validation of the dashboard experience beyond vendor docs.

   • [claimed-docs] “Get instant visibility into every robot in your fleet. Set up alerts for anomalies, track mission progress, and respond to issues before the…”
   • [claimed-docs] “One view across every vendor's fleet — AMRs, quadrupeds, humanoids, arms — without a separate dashboard, update cycle, or incident format pe…”
   • [claimed-docs] “Tracks historical performance per robot, per mission — speed, error rates, how a given unit has handled a given job before — alongside curre…”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice. Using built-in vis…”
   • [claimed-docs] “Manage multiple fleets simultaneously from a single operator view”

   proof ↗⚑ flag

   ROS 2—none0/10

   ROS 2 evidence covers single-robot/graph introspection (CLI tools, RViz via desktop install, topic/service introspection) but nothing about a unified dashboard aggregating health, location, and status across a whole fleet of robots — fleet-level monitoring is typically built by third-party layers on top of ROS 2, not documented here.

   • [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] “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

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

   weight 2 · round to Formant
   Formant~partialprobed6/10

   Formant exposes broad API/SDK surfaces (Agent SDK, Cloud SDK, Admin API, RealtimeSDK, webhooks, custom commands) covering telemetry, teleop, commands, and data export, and the toolkit lets developers embed/build custom apps mirroring UI functionality. However, some UI-centric features (fleet orchestration dashboards, AI assistant chat, analytics dashboard builder, alerting UI) are not clearly exposed as documented API endpoints, and no public OpenAPI spec was found (probe returned 404s), making full UI-parity via API unverifiable. missing for 10: a published OpenAPI/API reference proving full endpoint parity, API access to fleet-orchestration/AI-assistant/analytics-dashboard features, and independent confirmation of complete UI-to-API parity.

   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [github] “Embed your own application in Formant”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “A webhook allows you to make an API call to any endpoint over HTTP based on a trigger from a Formant event.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   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 userExport all of my data in open formats and leave

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

   Formant provides a documented Python Cloud SDK and query API specifically for exporting telemetry data, and an ingestion API for getting data in, suggesting some data portability. However, there is no explicit documentation of exporting *all* account data, no stated open-format guarantees (e.g., CSV/JSON/Parquet), and no discussion of account closure/data portability policy. Missing for 10: explicit 'export all data' workflow, named open file formats, and confirmation of no vendor lock-in upon leaving.

   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”

   proof ↗⚑ flag

   ROS 2~partialclaimed6/10

   ROS 2 is fully open-source with rosbag recording/playback and a Python API for reading/writing bag data, meaning all system data lives in inspectable, non-proprietary formats accessible via CLI or code, and there's no vendor SaaS lock-in to 'leave' from since it runs locally. However, the evidence never explicitly addresses bulk data export, format standardization/versioning guarantees, or migration tooling framed as 'export and leave'. Missing for 10: explicit documentation on bag format portability/interoperability guarantees, an explicit statement on no lock-in or data export completeness, and independent confirmation that recorded data is fully portable across tools/versions.

   • [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”
   • [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 userRead the product's source under an open license

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

   Evidence shows only a client-side toolkit/SDK repo (FormantIO/toolkit) for building integrations against Formant's APIs, not the platform's own source code, and no license is mentioned anywhere. Formant is a closed commercial SaaS robotics platform with no indication its core source is open or licensed for reading.

   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [github] “UI custom elements to make your application visually look similar to Formant's ecosystem”
   • [github] “Embed your own application in Formant”

   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

4. ai-native userSelf-host the core product

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

   Formant is a cloud-hosted SaaS platform; the evidence shows only an on-device agent (Docker-installed) and SDKs that connect to Formant's cloud, with no documentation of a self-hostable core platform/backend. No mention of on-prem or self-hosted deployment options anywhere in the docs or GitHub toolkit.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “configure devices, design custom views and modules, and build a backend for your custom application.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.formant.io/llms.txt # Formant Documentation > The Formant software platform allows companies to ru…”

   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

1. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Formant—none0/10

   Formant is a robotics fleet management platform whose core function is telemetry ingestion; no evidence in the pack addresses any opt-out mechanism for telemetry/usage tracking related to the product's own analytics or data collection about users/AI-native usage.

   ⚑ flag

   ROS 2—none0/10

   The evidence pack contains no mention of telemetry, usage tracking, or any opt-out mechanism for ROS 2; documentation covers middleware, QoS, CLI tools, and security but nothing about data collection practices. Since telemetry controls are a plausible axis for any software toolchain and no evidence confirms or denies its presence, this is 'none' rather than 'na'.

   ⚑ 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
   Formant—none0/10

   The evidence pack covers telemetry, commands, teleoperation, analytics, and fleet orchestration but contains no mention of roles, permissions, access control, or user/team management features that would let an ops lead restrict who can command, configure, or view robots.

   ⚑ 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
   Formant—none0/10

   The evidence pack covers teleoperation, commands, telemetry, fleet orchestration, and analytics, but contains no mention of emergency-stop or safety-interlock patterns, safety certifications, or documented safety-critical control flows. Since fleet-management/robotics-ops platforms are a fair category for this axis, absence of any e-stop/safety-interlock documentation yields 'none'.

   ⚑ 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

3. ops leadMy robots keep operating and buffer data locally when cloud connectivity drops, then recover cleanly

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

   The evidence describes the Formant agent, telemetry ingestion, and data rate-limiting, but nothing states that robots continue operating autonomously or buffer data locally during a cloud connectivity outage and then resync on reconnection. This is a reasonable expectation for an edge agent supporting fleet operations, but no documentation or GitHub evidence confirms offline buffering/recovery behavior.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “Each data stream can be rate-limited, so you don't need to ingest data at high resolution if you don't need it.”

   proof ↗⚑ flag

   ROS 2~partialclaimed3/10

   ROS 2's QoS policies (reliable/best-effort spanning TCP-to-UDP behavior) are explicitly designed to handle non-ideal networks, and rosbag tooling lets nodes record/buffer data locally, which are adjacent capabilities to 'operate offline and buffer data.' However, there is no documented feature specifically addressing cloud-connectivity loss detection, local buffering during an outage, or a clean reconnection/sync-recovery workflow — the evidence is about node-to-node DDS network resilience, not cloud uplink resilience. missing for 10: explicit cloud-connectivity-loss handling, local buffering-for-cloud-sync mechanism, and documented clean-recovery-on-reconnect behavior.

   • [claimed-docs] “Quality of service settings for handling non-ideal networks”
   • [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 can be as reliable as TCP or as best-effort as UDP, with many, many possible states in between”
   • [claimed-docs] “With the right set of Quality of Service policies, ROS 2 can be as reliable as TCP or as best-effort as UDP, with many, many possible states…”
   • [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

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 drawn
   Formant~partialprobed5/10

   Formant provides an Agent SDK and Cloud SDK/API that let external programs authenticate, ingest telemetry, and send commands to control real robots (formant-docs-2, formant-docs-4, formant-docs-9, formant-gh-1), which supports end-to-end robot commanding via SDK. However, there is no evidence of scoped/limited-permission credentials or AI-agent-specific auth mechanisms, and the OpenAPI spec probe returned 404s, suggesting the API surface isn't fully documented for programmatic discovery. Missing for 10: explicit scoped-credential/auth-token documentation, AI-agent-specific integration examples, and a public OpenAPI/machine-readable API spec.

   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”
   • [claimed-docs] “Commands tell our robot to take a predefined action. For example, we can use commands to trigger data ingestion, run a script, or tell our r…”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.formant.io/openapi.json, https://docs.formant.io/swagger.json, https://docs.formant.io/…”

   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
   Formant—none0/10

   Formant's docs describe an Agent SDK/Cloud SDK for telemetry ingestion, commands, and teleoperation, plus AI-assisted dashboards/orchestration, but there is no evidence of tooling specifically for integrating vision-language-action or robotics foundation models into a robot's autonomy stack.

   ⚑ 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
   Formant~partialclaimed4/10

   Formant offers a Python Cloud SDK, an Agent SDK, and a JS/TS-based RealtimeSDK/toolkit for building custom apps, but there is no evidence of official Go or C++ SDKs, nor any claim that these are strongly typed or cover the platform's 'full surface' (fleet orchestration, analytics, teleop APIs are referenced mostly via REST/Admin API, not dedicated SDKs). missing for 10: Go SDK, C++ SDK, explicit typing guarantees, and full API-surface coverage beyond telemetry/commands/data export.

   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “The primary programmatic way data scientists query for telemetry data is via the Cloud SDK, a lightweight Python module which can interact w…”
   • [claimed-docs] “The primary way of ingesting arbitrary data that is not via the Formant agent is with the Cloud SDK, a lightweight Python module which can i…”
   • [github] “Create your own application that uses Formant's APIs and RealtimeSDK for data”
   • [claimed-docs] “In addition to these commands, you can create custom commands via the Formant Admin API.”

   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

Teleop

1. ops leadRoute autonomy failures to a human intervention queue where an operator resolves and hands back control

   weight 1 · round to Formant
   Formant~partialclaimed5/10

   Formant supports alerting on anomalies, dispatching help when 'something looks wrong,' and time-synced 'intervention records,' plus teleoperation for operators to take direct control, suggesting an intervention workflow exists. However there is no explicit documentation of a dedicated human-intervention queue, assignment/resolution workflow, or an automated hand-back-to-autonomy mechanism after operator resolution. Missing for 10: explicit intervention-queue UI/workflow docs, operator resolution/hand-back-to-autonomy mechanics, and independent confirmation of this specific failure-routing flow.

   • [claimed-docs] “Get instant visibility into every robot in your fleet. Set up alerts for anomalies, track mission progress, and respond to issues before the…”
   • [claimed-docs] “Time-synced video, sensor, and intervention records for your team, and, where you choose, scoped research partnerships.”
   • [claimed-docs] “Assigns the right job to the right robot — regardless of who built it — using operational history and live data, and dispatches help the mom…”
   • [claimed-docs] “Build better human-to-robot ratios by automating incident response and creating workflows for monitoring devices at scale.”
   • [claimed-docs] “Formant's teleoperation provides a secure peer-to-peer connection that enables operators to control any aspect of a system.”
   • [claimed-docs] “Heterogeneous Fleet Orchestration assigns the right job to the right robot — regardless of who built it — using operational history and live…”

   proof ↗⚑ flag

   ROS 2—none0/10

   ROS 2 provides low-level building blocks (actions with feedback/cancel, lifecycle-managed nodes, topics) that could underpin a human-intervention workflow, but the evidence pack shows no actual feature for detecting autonomy failures, routing them to an operator queue, or handing control back after resolution — that is an application-layer capability ROS 2 does not ship out of the box. Missing for 10: any documentation of a fault-detection/escalation mechanism, an intervention-queue or ticketing construct, or operator handback protocol.

   • [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] “Topics: For continuous data streams. Services: For synchronous request/response interactions. Actions: For long-running tasks with feedback”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Formant✓fullclaimed8/10

   Formant provides remote observability via the Agent SDK ingesting telemetry, an Observe view for live data, Analytics for historical/aggregated queries with custom SQL, and ROS/Docker agent installation for deployed robots, all matching remote debugging of topics/logs/state. missing for 10: no explicit mention of raw log tailing or independent third-party hands-on validation of the debugging workflow.

   • [claimed-docs] “This guide will teach you how to install the Formant agent to your device via Docker.”
   • [claimed-docs] “The Agent SDK client contains a suite of methods which allow you to ingest telemetry data, receive and respond to commands, teleoperate your…”
   • [claimed-docs] “Get instant visibility into every robot in your fleet. Set up alerts for anomalies, track mission progress, and respond to issues before the…”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice.”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice. Using built-in vis…”
   • [claimed-docs] “Each data stream can be rate-limited, so you don't need to ingest data at high resolution if you don't need it.”

   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

3. ops leadTeleoperate a remote robot with live video and responsive control over real-world networks

   weight 3 · round to Formant
   Formant✓fullclaimed8/10

   Formant explicitly documents low-latency, peer-to-peer teleoperation with joystick/button control, configurable teleop interfaces, and secure remote control over real-world networks, plus live video/sensor visualization via Analytics and Observe views. Missing for 10: independent/hands-on network-performance validation and detail on video streaming latency/quality under adverse network conditions beyond vendor claims.

   • [claimed-docs] “Reliable, low-latency teleoperation over a peer-to-peer connection keeps your operations moving — via joystick, buttons, or custom controls.”
   • [claimed-docs] “Control robot devices from anywhere over a low-latency, peer-to-peer connection, via joystick and buttons.”
   • [claimed-docs] “Formant's teleoperation provides a secure peer-to-peer connection that enables operators to control any aspect of a system.”
   • [claimed-docs] “Configure teleop interfaces to meet the needs of your specific use case.”
   • [claimed-docs] “We can send commands with the click of a button from the Observe view, or during teleoperation.”
   • [claimed-docs] “Formant Analytics allows you to visualize, aggregate, and analyze data from your device over a time range of your choice. Using built-in vis…”

   proof ↗⚑ flag

   ROS 2~partialcommunity5/10

   ROS 2's QoS policies (reliable/best-effort tuning for non-ideal networks), pub/sub topics for continuous sensor/video streams, and actions for long-running feedback-driven tasks provide the underlying building blocks for teleoperation, and a community user explicitly notes ROS gives teleop 'for free' via its ecosystem conventions [ros2-comm-9]. However, there is no first-party documentation of a video-streaming pipeline, latency benchmarks over real-world/lossy networks, or a dedicated teleop stack/tooling in this evidence pack. missing for 10: dedicated video transport/compression tooling (e.g., image_transport/web video), real-network latency/responsiveness benchmarks, explicit teleoperation reference architecture or case study.

   • [claimed-docs] “Quality of service settings for handling non-ideal networks”
   • [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] “Actions allow clients to send goals, receive feedback during the execution, cancel if needed, and return a result if availabl”
   • [claimed-docs] “The topic interface is meant for continuous data streams, for example, streaming sensor data or the status of your robot.”
   • [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