Review fixture 02 · Source-mapped · Independent human review pending T-041 / Profile 02
artificially.cloud
Directory
T-041
06 sources

Published recordSources checked

Technologies / Industrial mobile manipulation

Agility Digit + Arc

A humanoid robot and fleet platform with a documented commercial warehouse workflow—credible evidence of bounded work, not a general artificial worker.

Canonical record
technology-agility-digit-arc

Sources checked


Next review

01 / Identity
System, not silhouette

Canonical profile

The deployed object includes the building around it.

Digit is the mobile manipulation robot. Arc is the vendor’s fleet and workflow platform. The documented GXO workflow concerns Digit 4; Agility’s September 2026 announcement identifies Digit 5 as the next generation and still frames its availability prospectively. This profile does not treat Digit 5 as the deployed GXO system.

Object type
Humanoid mobile manipulator + fleet orchestration platform
Responsible organization
Agility Robotics
Domain
Embodied AI and industrial robotics
Human system
Warehousing, manufacturing, logistics, and work design
Geography
Named customer deployment in the United States; other availability not independently mapped
Verified workflow
Moving totes from mobile robots to conveyors in a live warehouse
Generation boundary
Digit 4 deployment evidence; Digit 5 announced, not established here as deployed
Access
Enterprise deployment or Robots-as-a-Service; no public pricing verified
Last verified

What is established

A bounded system doing paid work.

GXO and Agility announced a multi-year Robots-as-a-Service agreement for Digit in regular warehouse operations. The named task moves totes from other mobile robots to conveyors, coordinated through Arc; Agility’s later generation record identifies the deployed generation as Digit 4.

What is not established

An unrestricted artificial worker.

The mapped evidence does not establish human-equivalent job breadth, consumer readiness, unsupervised operation across arbitrary sites, broad adoption, workforce substitution, or independently verified economics.

02 / State
Four dimensions

Technology state · as of 15 Oct 2026

Deployed is not general.

A commercial workflow is stronger evidence than a demonstration. It still describes one system, one class of task, named sites, and evidence produced by the parties involved.

Development
Digit 4 deployed in bounded workThe named warehouse workflow concerns Digit 4. Digit 5 availability remained forward-looking at the cutoff.
Availability
Enterprise deployment or RaaSNo consumer availability or public price is established in the mapped record.
Adoption
Not independently assessedOne documented customer workflow does not establish market-wide deployment.
Lifecycle
Digit 4 active; Digit 5 announcedDigit 5 specifications, safety features, availability dates, order claims, and scale claims are volatile vendor statements excluded from this assessment.

Operational envelope

The job extends beyond the body.

Facility mapping, workflow definition, system integration, charging, connectivity, monitoring, safety controls, maintenance, and exception handling are part of the deployed capability. Removing them changes the claim.

03 / Ledger
Claims and limits

Capability / limitation

Every visible behavior rests on invisible work.

The left side records what the source set supports. The right side records what should not be inferred from it.

C-01 · Customer-confirmed deployment

Digit performs a named tote-transfer workflow.

GXO’s release describes Digit taking totes from autonomous mobile robots and placing them onto conveyors in regular warehouse operations.

Sources GXO release · Agility Arc release · Digit 5 generation announcement

L-01 · Material limitation

One workflow is not general-purpose work.

The evidence does not establish unrestricted item handling, arbitrary route planning, broad site transfer, or competence across warehouse roles.

C-02 · Vendor-described infrastructure

Arc maps, defines, manages, and troubleshoots.

Agility describes Arc as supporting facility mapping, workflow definition, operational management, and troubleshooting for deployed robots.

Source Agility Arc release

L-02 · Material limitation

The robot is not a self-contained worker.

The mapped source does not quantify integration labor, intervention time, downtime, support burden, network dependency, or total cost per completed task.

C-03 · Physical compatibility

A human-scale body can use human-built interfaces.

Legs, reach, and mobile manipulation may let one platform approach aisles, shelves, carts, and conveyors originally arranged around people.

Evidence Documented workflow + vendor design intent

L-03 · Material limitation

Human scale is not human equivalence.

The silhouette does not establish human dexterity, judgment, adaptability, stopping behavior, or safe operation in every human environment.

04 / Capability lens
05 of 07 verbs

Where the system enters

Sense. Infer. Decide. Act. Explain.

These verbs locate the record across Artificially.cloud concepts. They are an editorial reading tool, not a vendor architecture, safety taxonomy, or claim that one component performs each behavior alone.

  1. 01

    Sense

    The robot must perceive objects, routes, people, and changing obstacles.

  2. 02

    Infer

    Perception must become a claim about object identity, pose, path, or task state.

  3. 04

    Decide

    Control and workflow systems select a next action or a reason to pause.

  4. 05

    Act

    Walking, grasping, carrying, and placing alter the physical workplace.

  5. 06

    Explain

    Operators need legible state, exceptions, and recovery information; the quality of that account is not independently assessed here.

05 / Evidence Margin
06 records

Provenance and absence

The deployment is direct evidence. It is not independent evidence.

The customer and vendor directly establish their agreement and named workflow. Independent performance, safety, labor, economic, and adoption evidence is not attached to this record.

Support
Direct records support a bounded live workflow and the vendor-described orchestration layer
Agreement
Not assessed across independent deployment studies
Directness
Direct for agreement and reported workflow; indirect for performance and outcome
Independence
Low for product claims; regulator guidance and government research independently frame general risk and measurement questions
  1. source-gxo-digit-deploymentGXO agreement with Agility RoboticsCustomer release · bounded warehouse workflow
  2. source-agility-arcAgility Arc fleet orchestration platformVendor platform release · integration and management claims
  3. source-agility-faqAgility Robotics FAQVendor documentation · access and product context
  4. source-agility-digit-5-announcementAgility unveils Digit 5Vendor generation record · Digit 4 deployment / Digit 5 announcement boundary
  5. source-osha-roboticsRobotics - OverviewU.S. regulator guidance · workplace-hazard context
  6. source-nist-hriPerformance of Human-Robot InteractionGovernment measurement program · interaction and integration questions

06 / Past → Present → Possible

From artificial worker to bounded work system.

The relationship is thematic and comparative. R.U.R. does not establish prediction, causality, or technical influence on Digit.

  1. / Past

    Fiction manufactures a universal workforce.

    Čapek’s synthetic workers make artificial labor an industrial and political system.

    Inspect the historical comparison →
  2. / Present

    A humanoid performs one documented transfer.

    Digit’s bounded tote workflow is credible evidence of useful work without establishing generality.

    Inspect the dated assessment →
  3. Next review / Research question

    What survives outside the first job?

    Look for independent task, site, intervention, recovery, safety, and economics evidence rather than a broader label.

    Open the research windows →

What would change this record?

Questions for the next review.

Scheduled for , or earlier after a material deployment, safety, product-state, or correction record.

  1. 01

    How many materially different workflows are in sustained customer operation?

  2. 02

    What is the intervention time per productive robot hour over thousands of cycles?

  3. 03

    Which capabilities transfer between sites without hardware changes or extensive retraining?

  4. 04

    What application-specific safety evidence is available beyond vendor description?

  5. 05

    What is the complete cost per task after integration, supervision, downtime, maintenance, and connectivity?

  6. 06

    Which operational and sensor data leaves the site, and who can inspect that boundary?

Related concept and story

Atlas — Trace The Working Body from fiction to a bounded shift →

Story — Read why the job matters more than the silhouette →

Related placement describes an editorial relationship. It does not assert endorsement, interoperability, or technical lineage.