Robot product dossier · 12

Gemini Robotics 1.5 and ER 1.6

Google DeepMind · Developer access and selected partners · VLA and embodied reasoning models

Research / demonstrationResearch and developer-access models; access, hardware support and production readiness varyLast reviewed: 11 August 2026

Decision questionHow can a robotics team test whether a foundation model transfers beyond its published demonstrations?

12

FUURAA thesis

Gemini Robotics 1.5 and ER 1.6 are best treated as model-layer capabilities, not complete robot products. Their value appears only through hardware, sensing, control, safety and evaluation supplied by a wider system.

Reading method

Do not ask only what the robot can do; ask how the whole system works, fails and recovers.

01Stage

Separate commercial, limited, prototype and development stages.

02System

Inventory software, payloads, facilities and people beyond the robot.

03Evidence

Move from demos to repeated tests, field data and auditable records.

04Boundary

State what first-party reporting still cannot prove.

System and workflow map

Four interdependent layers turn a product name into real operating conditions.

Each layer explains its role and what procurement, research or deployment teams should watch.

01

Multimodal reasoning

Models interpret language, visual context and task goals.

02

Embodied action

Model outputs must be grounded into actions supported by a robot.

03

Hardware adaptation

Transfer across embodiments requires calibration, data and interface work.

04

Safety wrapper

Independent constraints and monitors are needed around probabilistic outputs.

Decision checklist

Five checks turn product interest into verifiable procurement, research or pilot questions.

Define the task, interfaces, safety and operations before requesting evidence that supports a decision.

  1. 01

    Task fit

    Choose a task suite with seen, shifted and genuinely novel variants.

  2. 02

    Integration load

    Map cameras, robot APIs, control rate, compute, network and data governance.

  3. 03

    Safety case

    Keep safety-critical limits outside unconstrained model generation.

  4. 04

    Operating model

    Plan prompt, data, model-version, monitoring and fallback ownership.

  5. 05

    Evidence to request

    Request success distributions, latency, interventions, unsafe proposals and cross-robot results.

Scope boundaries

Product availability, a video demonstration or a commercial agreement each supports only bounded conclusions.

Sources and evidence status

Primary product material and independent evaluation context are kept distinct.

Dates, source identity, supported conclusions and reading boundaries remain reviewable.