Full resource library

Browse by deployment task

Optional filters

Showing 12 of 110 approved resources

• Guides

  U.S. Restrictions on New Chinese Robots: What Deployment Teams Need to Document

  As reported on July 28, 2026, U.S. restrictions on certain Chinese-manufactured humanoid and quadruped robots require deployment teams to establish documented provenance, configuration baselines, and network access records for every affected system.

• Evidence

  Robot Deployment Provenance: A Documentation Guide

  Robot deployment provenance is the structured record of a robot system's origin, component history, software lineage, and network relationships. This guide covers what to capture, when to capture it, and how to maintain the record through system changes.

• Evidence

  Robot Country of Origin Evidence: What to Capture and How

  Country of origin evidence for robot deployments covers the manufacturing location of the complete system and its major components. This guide explains what constitutes primary origin evidence, how to handle ambiguous or mixed origins, and how to maintain the record through supply chain changes.

• Evidence

  Robot Manufacturer Verification: Documentation and Evidence Guide

  Robot manufacturer verification establishes the legal identity, ownership structure, and corporate relationships of the entity that built a deployed robot system. This guide covers what verification covers, how to document it, and how to handle manufacturer changes or ambiguous affiliations.

• Evidence

  Robot Component Provenance: Subsystem Documentation Guide

  Robot component provenance records the manufacturer, origin, and identity of the major subsystems and components in a deployed robot. This guide covers which components to document, how to obtain origin information, and how to manage the record through substitutions and replacements.

• Evidence

  Robot Supply Chain Evidence: A Deployment Documentation Guide

  Robot supply chain evidence documents the sourcing relationships behind a deployed robot system. This guide covers what supply chain evidence covers, how to build it from available sources, and how to document gaps when supply chain information is unavailable.

• Evidence

  Robot Deployment Configuration Baseline: A Practical Guide

  A robot deployment configuration baseline is the verified record of a robot system's complete configuration state at a defined point in the deployment lifecycle. This guide covers what to include, when to capture it, and how to use it for troubleshooting and acceptance decisions.

• Evidence

  Robot Firmware Version Verification: A Deployment Evidence Guide

  Robot firmware version verification establishes the version identity of all firmware layers running on a deployed robot system. This guide covers verification methods, documentation standards, and how to maintain the firmware version record through updates and component changes.

• Evidence

  Robot Software Version Verification: A Deployment Evidence Guide

  Robot software version verification documents the complete software stack running on a deployed robot system. This guide covers which software layers to verify, verification methods, and how to maintain version records through updates and configuration changes.

• Evidence

  Robot Configuration Change Control: A Deployment Process Guide

  Configuration change control for robot deployments is the process of formally recording, reviewing, and tracking every configuration modification that affects a robot system during its deployment lifecycle. This guide covers change record requirements, change management integration, and how change control supports acceptance and post-acceptance investigations.

• Evidence

  Robot Configuration Drift: Detection and Remediation Guide

  Robot configuration drift occurs when a deployed robot's actual configuration diverges from its documented baseline through incremental undocumented changes. This guide covers how drift accumulates, how to detect it, how to document the drifted state, and how to remediate it before it blocks acceptance or causes post-acceptance failures.

• Evidence

  Robot Controller Replacement Retesting: A Deployment Protocol Guide

  When a robot's main controller or a major controller subsystem is replaced, retesting is required to confirm that the replacement has not changed the system's acceptance-verified behavior. This guide covers what retesting scope a controller replacement requires, what evidence to capture, and how to update the acceptance record.