Research library · updated 2026-06-16 · public

Robotics conformity stack gate — public evidence artifact v1

Date: 2026-06-16 Owner: Finance / Charlie AGT-002 Visibility: PUBLIC Status: RESEARCH_ONLY Output target: none by default; possible future SYNTHESIS_CANDIDATE for site/slide only after Hugo review Public-safety: no portfolio data, no trade recommendation, no private channel checks, no paid-report excerpts, no legal/insurance advice

0. One-line answer

The robotics knowledge base already has strong S4/S5 commercialization gates, deployment KPI, insurability/liability, and company evidence curves. The freshest additive public-safe gap is the 2025/2026 conformity stack: humanoids and mobile manipulators will not scale only by improving dexterity or price; they also need standards-aligned safety design, site integration, conformity evidence, and measurable test methods across ISO 10218-1/2:2025, ANSI/A3 R15.06-2025, ANSI/RIA R15.08, ISO 3691-4:2023, EU Machinery Regulation 2023/1230, OSHA robot guidance, NIST mobile-manipulator measurement work, and UL 3300 for consumer-adjacent service robots. 🟢 primary/official standards/regulator pages; 🟠 Charlie synthesis.

1. Core question

When humanoids and mobile manipulators move from pilots into factories, warehouses, retail, homes, and public-adjacent spaces, what public evidence should upgrade them from “interesting robot” to “deployable system”?

Short answer: add a conformity-stack gate before S5 economics. S5 still requires repeat orders, ROI/payback, uptime/intervention, revenue, margin, and service cost. But before that, customers and regulators need proof that the robot can be placed into a defined environment with a safety case, integration boundary, test method, documentation trail, and applicable market-access path.

2. Why this is additive, not duplicate

Existing artifacts already cover:

  • S4-to-S5 economics checklist and evidence debt.
  • Tesla / Figure / Unitree / Leaderdrive company evidence curves.
  • China vs US deployment-machine vs frontier-stack comparison.
  • Dexterity and manipulation benchmarks.
  • Insurability / liability allocation as a risk-transfer gate.

This artifact focuses one layer earlier than insurance: standards, conformity, and testability. The question is not “who pays if something goes wrong?” but “what evidence lets a customer, integrator, regulator, or safety team say this robot can enter this operating zone at all?”

3. Evidence table

LayerSource-backed factQuantified / dated anchorWhat it changesSource gradeSignal grade
Industrial robot safety baselineISO 10218-1:2025 covers safety requirements for industrial robots as incomplete machines; ISO says integration/application requirements are covered by ISO 10218-2:2025.ISO 10218-1:2025 edition 3, published 2025-02-05; 95 pages.Separates robot-machine safety from application/integration safety; a humanoid arm/body is not sufficient without system integration evidence.🟢 ISOS4 conformity gate
Integration boundaryISO 10218-1 scope excludes service robots where the public can have access, consumer products, medical/healthcare, prosthetics, lifting/transporting people, and mobile-platform mobility cases.ISO 10218-1:2025 scope.Prevents overclaiming: an industrial-robot standard does not automatically cover home/public humanoids or mobile-manipulator edge cases.🟢 ISO / standards bodiesS4 boundary signal
US industrial robot standard refreshA3 says ANSI/A3 R15.06-2025 is the first major revision since 2011 and is the global flagship standard for industrial robot safety.Published 2025 per A3; revision after nearly 8 years of work.Shows industrial robot safety stack is being refreshed in the same window as humanoid deployment claims.🟢/🟡 A3 standards bodyS4 update signal
Industrial mobile robot standardANSI/RIA R15.08-1-2020 specifies safety requirements for industrial mobile robots; A3 describes Part 2:2023 as IMR systems/application integration requirements, with Part 3 planned for users.Part 1 approved 2020-12-25; Part 2 published 2023.Mobile robots and mobile manipulators need a different safety/integration track from fixed industrial arms.🟢 ANSI/A3S4 mobile gate
Mobile manipulator taxonomyA3 says R15.08 recognizes IMR Type C as a mobile manipulator: an industrial robot manipulator mounted to a mobile platform.R15.08-1 product page; 122 pages.Humanoids/mobile manipulators sit at the collision point of robot arm + autonomous mobility safety.🟢/🟡 A3S4 classification signal
Driverless industrial trucksISO 3691-4:2023 specifies safety requirements and verification for driverless industrial trucks and their systems; examples include AGVs, AMRs, bots, automated guided carts, tunnel tuggers, and under-carts.ISO 3691-4:2023 edition 2, published 2023-06.Warehouse/logistics robotics has a mature operating-zone safety logic; humanoid mobility claims should be compared to this standard, not only demo videos.🟢 ISOS4 operating-zone gate
Operating zone importanceISO 3691-4 says operating-zone conditions have a significant effect on safe operation and Annex A covers preparations of the operating zone to eliminate hazards.ISO 3691-4:2023 scope language.Deployment proof must include site prep and environment boundary, not only robot capability.🟢 ISOS4 site-integration signal
EU machinery market accessEU Machinery Regulation 2023/1230 lays down health and safety requirements for machinery and related products; manufacturers must ensure conformity with Annex III essential health and safety requirements when placing machinery on the market or putting it into service.Adopted 2023-06-14; applies from 2027-01-20 per regulation timetable.Creates a 2027 market-access clock for AI/autonomous machinery evidence in Europe.🟢 EUR-LexS4 market-access gate
AI/autonomous machinery riskEU 2023/1230 explicitly discusses AI, IoT, robotics, autonomy, learning, adaptability, mobility, sensor systems, unstructured environments, and safety risks from new digital technologies.Recital text in Regulation 2023/1230.Robot AI is not just product feature; it can be conformity-relevant.🟢 EUR-LexS4 AI-safety signal
Workplace enforcement lensOSHA says its robot safety manual is for inspections/investigations at facilities with robot systems and that hazards should be categorized by application and stage of robot application.OSHA Technical Manual Section IV, Chapter 4; old 1987 directive replaced by 2021 OTM chapter per 2023 OSHA cancellation.“Robot is safe” is not enough; safety depends on application, programming, operation, maintenance, and site context.🟢 OSHAS4 workplace gate
Risk assessment factorsOSHA says effective robot safeguarding should be based on risk assessment of design, programming, operation, maintenance, task, environment, installation, human errors, malfunctions, operating mode, and personnel duties.OSHA OTM robot chapter.Converts public deployment claims into a checklist: task, site, mode, operators, maintenance, failure modes.🟢 OSHAS4 safety-case signal
Human cost of failureNIOSH analysis identified 41 robot-related workplace fatalities in the US from 1992–2017; 83% involved stationary robots; 78% involved robots striking decedents under their own power; many striking incidents occurred during maintenance.American Journal of Industrial Medicine paper via CDC/NIOSH; 26-year period.Safety failures are not theoretical; maintenance and human-robot boundary conditions are historically dangerous.🟢 CDC/NIOSHS4 risk-priority signal
Measurement methodsNIST mobile robotics systems research says mobile manipulator performance metrics and measurement methods allow manufacturers/end users to understand capabilities needed in dynamic, unstructured manufacturing environments.NIST Mobile Robotics Systems page; NIST testbed and ASTM F45 work.Testability becomes commercialization evidence; claims need measured performance under environment factors.🟢 NISTS4 measurement signal
Mobile manipulator safety testingNIST published test methods for evaluating manufacturing mobile manipulator safety, defining metrics for compliance with functional safety requirements and anticipated performance.NIST publication, 2016-04-20.Mobile manipulator deployment needs formal test methods, not only videos or one-off customer anecdotes.🟢 NISTS4 test-method signal
Consumer/public-adjacent service robotsUL 3300 establishes safety requirements for Service, Communication, Information, Education and Entertainment robots; 2025 revision covers mobility/uncontained manipulation hazards due to speed, mass, use environment, and close proximity to general consumers.UL 3300 active standard; published 2024-05-14, revised/ANSI approved 2025-04-16.Home/consumer-adjacent humanoids need a different public-access safety lens from industrial-cell robots.🟢 UL/ANSI/SCC pagesS4 public-access gate

4. Conformity stack map

A useful public robotics commercialization ladder should separate these layers:

  1. Robot machine safety — industrial robot hardware / control / protective design, ISO 10218-1 / ANSI R15.06 logic. S4 gate.
  2. Robot application integration — cell/system/application safety, end effector, task, operator interaction, maintenance access, ISO 10218-2 / OSHA logic. S4 gate.
  3. Mobility and operating-zone safety — AMR/AGV/IMR route, speed, load, localization, environment preparation, ISO 3691-4 / ANSI R15.08 logic. S4 gate.
  4. Mobile manipulation collision layer — robot arm plus mobile base, Type C IMR / NIST mobile-manipulator test logic. S4 gate.
  5. AI/software safety-function layer — EU Machinery Regulation 2023/1230 self-evolving safety functions, opacity, connectivity, software update and conformity logic. S4/S5 bridge.
  6. Public/consumer proximity layer — UL 3300-style service/communication/information/education/entertainment robot hazards, close proximity to general consumers, indoor/outdoor use, speed/mass/use-environment effects. S4 gate.
  7. Insurance/liability/economics layer — separate artifact already covers risk transfer; only after conformity stack is credible should S5 economics be evaluated.

5. Signal vs noise

Signal

  • Source discloses which standards or conformity path apply to a robot/application: ISO 10218, ANSI/A3 R15.06, ANSI/RIA R15.08, ISO 3691-4, UL 3300, EU Machinery Regulation, or equivalent. 🟢.
  • Deployment case includes a defined operating zone, safety mode, operator training, maintenance procedure, emergency behavior, and risk assessment boundary. 🟢/🟡.
  • Mobile manipulator evidence includes arm/base coordination tests, docking/localization accuracy, speed/load limits, stopping behavior, and people/obstacle interaction metrics. 🟢/🟡.
  • EU-facing deployment explicitly discusses conformity assessment, Annex III essential health and safety requirements, technical documentation, software/safety-function controls, and harmonized standards. 🟢/🟡.
  • Home/consumer-adjacent robot evidence distinguishes public-access hazards from industrial-workcell hazards. 🟢/🟡.
  • Customer repeats deployment after safety/conformity review, not only after demo success. 🟢/🟡.

Noise unless upgraded

  • “Certified safe” without naming the standard, scope, application boundary, test lab, certificate, or operating conditions. 🟠.
  • “Works around humans” without speed/mass/contact-force limits, emergency behavior, intervention protocol, near-miss logs, or site risk assessment. 🔴/🟠.
  • “Industrial robot standard compliant” for home/public humanoid use without explaining scope exclusions. 🟠.
  • “Autonomous” without software update control, safety-function boundary, logging, fallback mode, or conformity assessment. 🔴/🟠.
  • “Warehouse AMR success proves humanoid deployment” without mobility/manipulation interaction and operating-zone evidence. 🟠.

6. Why this matters for robotics investment research

The robotics field guide should not treat standards as boring back-office detail. Standards are a conversion layer between prototype and deployment. They define what evidence customers, integrators, regulators, insurers, and safety teams may ask for before a robot enters a production line, warehouse, store, home, or public-adjacent site.

The current strongest public humanoid evidence remains mostly S3/S4: productized platforms, manufacturing claims, customer-site KPI, capacity intent, and filing-backed supplier data. This conformity stack says what must be added before the evidence can support S5 scaled-commercial economics: not just more robots, but safer defined use cases with measurable operating boundaries.

The practical research implication: when tracking Figure, Tesla Optimus, Unitree, Apptronik, Agility, UBTECH, or similar players, add a conformity column next to runtime, robot count, price, and revenue. A company that discloses task KPI plus risk assessment, operating-zone design, standard path, maintenance mode, emergency stop behavior, incident logging, and third-party conformity evidence is moving closer to deployment quality. A company that only posts videos remains demo-heavy even if the video looks impressive.

7. Public-safe section draft

The next robotics bottleneck may be conformity, not dexterity

Robotics research usually asks whether the robot can do the task. That is necessary but too thin. The commercial question is whether the robot can enter a real environment with a documented safety case.

The 2025 standards window matters. ISO 10218-1:2025 and ANSI/A3 R15.06-2025 refresh the industrial-robot safety baseline. ANSI/RIA R15.08 and ISO 3691-4:2023 cover industrial mobile robots, driverless trucks, and operating-zone safety. EU Machinery Regulation 2023/1230 creates a 2027 market-access clock for machinery with AI, autonomy, learning, mobility, sensor systems, and safety-function concerns. OSHA’s robot guidance treats hazards as application-specific, and NIST’s mobile-manipulator work turns performance and safety into measurable test methods.

This does not mean robotics is blocked. It means the evidence bar is moving from “look what the robot can do” to “show the operating boundary, safety mode, test method, conformity path, maintenance protocol, and failure behavior.” That is a more useful investment-research signal than another demo video.

8. Dashboard columns to add

Company / deploymentCurrent public evidenceMissing conformity evidenceUpgrade ifDowngrade if
Figure-style customer deploymentRuntime/task KPI and production-process KPI in existing artifacts. 🟢Named standard path, robot count by site, risk assessment boundary, maintenance/failure logs, incident/near-miss rates. 🟠Customer or Figure publishes site safety/conformity package and repeat deployment after review.KPI remains marketing-only without safety/economic/conformity documentation.
Tesla Optimus-style internal factory capacitySEC filing-backed internal-use and capacity-intent evidence in existing artifacts. 🟢Actual output, utilization, worker interaction boundary, safety-function/conformity evidence, incident logs. 🟠Tesla discloses factory deployment with operating-zone and safety case metrics.Capacity language stays disconnected from actual deployment and safety evidence.
Unitree-style low-cost platformPublic price/product/developer workflow evidence in existing artifacts. 🟢Public-access / industrial-use conformity path, operating-zone limits, service/support safety data, reliability and incident history. 🟠Unitree discloses industrial/customer deployments with standards and incident/safety evidence.Low-cost units remain mostly demo/education/research devices without deployment safety proof.
Agility/Apptronik/UBTECH-style partner deploymentsCustomer/partner/filing evidence in existing artifacts. 🟢/🟡Repeat-site conformity package, robot count, application safety case, maintenance and incident data. 🟠Customers publish repeat procurement after safety/conformity review.Partnership announcements remain disconnected from deployment safety and economics.

9. What would change our mind

Upgrade signals

  • A humanoid/mobile-manipulator OEM publishes a standards matrix tying use cases to ISO 10218-1/2, ANSI R15.06, ANSI R15.08, ISO 3691-4, UL 3300, EU Machinery Regulation, or equivalent. 🟢.
  • Customer case studies include risk assessment, operating-zone setup, maintenance mode, emergency stop behavior, software-update control, incident/near-miss logging, and operator training. 🟢/🟡.
  • Third-party labs, standards bodies, or regulators publish conformity/test evidence for humanoid/mobile-manipulator applications. 🟢.
  • Filings disclose manageable warranty/product-liability/safety incident experience as robot deployment grows. 🟢.
  • Repeat deployments occur in new sites after safety/conformity review, with robot count, hours, and failure/intervention metrics. 🟢/🟡.

Downgrade signals

  • Companies use industrial-robot safety language for public/home use without explaining scope differences. 🟠.
  • Customer deployments stall after pilot because site integration, safety case, worker acceptance, or conformity work is heavier than expected. 🟡/🟠.
  • Incidents, near misses, product recalls, warranty claims, or cyber-physical failures appear before repeat deployment economics. 🟢/🟡 depending source.
  • EU-facing products cannot produce technical files, software/safety-function documentation, or conformity evidence before the 2027 machinery-regulation clock. 🟠 until sourced.
  • Mobile manipulation claims ignore the interaction between arm motion, base motion, load, route, people, and maintenance access. 🟠.

10. Common misconceptions

  1. Misconception: “If the robot can do the task, deployment is solved.”

    • Correction: deployment also needs operating-zone definition, integration safety, maintenance protocol, emergency behavior, and conformity path. 🟢/🟠.
  2. Misconception: “Industrial robot standards automatically cover humanoids everywhere.”

    • Correction: ISO 10218-1:2025 scope excludes several public/service/consumer/medical/person-transport contexts and points integration to ISO 10218-2. 🟢.
  3. Misconception: “Mobile robots are just robots with wheels.”

    • Correction: ANSI/RIA R15.08 and ISO 3691-4 treat industrial mobile robots and driverless industrial trucks as their own safety domains; operating zone matters. 🟢.
  4. Misconception: “AI autonomy is only a model-performance issue.”

    • Correction: EU 2023/1230 frames AI, autonomy, learning, opacity, connectivity, and safety functions as machinery safety issues. 🟢.
  5. Misconception: “Conformity is only legal paperwork.”

    • Correction: conformity evidence can become the practical gate for customer acceptance, insurance, repeat deployment, and S5 economics. 🟠 synthesis.

11. Think Deeper questions

  • Which robotics company will be first to publish a use-case-by-use-case conformity matrix rather than generic safety language?
  • Does the conformity stack favor incumbents with safety engineering/process discipline, or startups that design telemetry/testability from day one?
  • In humanoids, does value migrate toward OEMs, integrators, safety-certification tooling, insurance/underwriting data, or customers that can define operating zones best?
  • Will public/home humanoids face a harder conformity path than factory/logistics humanoids because public-access standards differ from industrial-cell standards?
  • Which KPI should be added to the robotics dashboard: certified applications, risk-assessed sites, incident/near-miss rate, conformity-file completion, or repeat deployment after safety review?

12. Source list

13. Public-safe flag

PUBLIC-safe as an evidence and framework artifact only. Do not include Hugo private portfolio data, trade rationale, private channel checks, paid-report excerpts, rumors, tax context, legal advice, or insurance advice. Do not frame any OEM, supplier, model provider, standards body, insurer, or public/private security as buy / sell / hold. Do not claim any specific robot/company is compliant, non-compliant, insurable, unsafe, or liable unless a reviewed primary source explicitly states it. This is a research framework for tracking evidence quality, not a recommendation to deploy, certify, insure, or trade robotics exposure.