Track Google Gemini Live Translate and Robotics ER 2 previews

[a5c-ai]

Models

• Provider: Google Gemini
• Model IDs / versions: gemini-3.5-live-translate-preview, gemini-robotics-er-2-preview
• API family: Gemini API generateContent / Live / robotics-preview family as documented by Google AI for Developers.
• Release date: not shown in fetched model index; checked on 2026-08-13.
• Documentation: https://ai.google.dev/gemini-api/docs/models

Capabilities and limits

• Gemini 3.5 Live Translate: listed as endpoint gemini-3.5-live-translate-preview, described as live/streaming translation in the Gemini model index.
• Gemini Robotics ER 2: endpoint gemini-robotics-er-2-preview; Google describes it as an embodied reasoning model for advanced video understanding, spatial reasoning, multi-step tool orchestration, and multi-robot collaboration for robotics tasks.
• Context windows: not available in the extracted model index for these preview entries; implementation should check detail pages/API metadata.
• Pricing: not available in the extracted model index; implementation should check Gemini API pricing docs.
• Vertex availability: likely needs separate Vertex/Gemini Enterprise verification; no cross-provider assertion made in this sweep.
• Azure/Bedrock availability: no evidence found.

Graph work needed

• Add ModelVersion records or claims for gemini-3.5-live-translate-preview and gemini-robotics-er-2-preview.
• Add modality/capability claims for live translation, video/spatial/robotics reasoning, tool orchestration, and preview lifecycle.
• Connect to Google provider version and Gemini API transport edges; robotics/live preview APIs may require more specific protocol edges than normal generateContent.
• Transport-adapter proxy: verify live-streaming translation and robotics-preview support. Existing Gemini generateContent support may not cover these APIs.

Sweep notes

• Existing open issues checked: no dedicated issues found for gemini-3.5-live-translate-preview or gemini-robotics-er-2-preview. Gemini 3.6 / 3.5 Flash-Lite updates are already tracked by Track Gemini 3.6 Flash #1623 and Track Google Gemini 3.6 Flash and Gemini 3.5 Flash-Lite/Cyber #1626.

[a5c-ai]

Triage Summary

• One-line: Add evidence-backed Atlas graph coverage for Google Gemini Live Translate and Robotics ER 2 preview model IDs, with adapter/transport support represented conservatively.

Critical Evaluation

• Reporter analysis needs correction: this is valid model-version work, but Live Translate partially overlaps closed Track Google Gemini 3.5 Live Translate Preview #1002. The distinct untracked scope is gemini-robotics-er-2-preview, and the current tree still has no exact records for either issue model ID.
• This is an enhancement/catalog freshness issue, not a runtime bug.
• Do not infer standard generateContent support for these specialized preview APIs without explicit evidence or adapter implementation.

Root Cause Analysis

• Repository searches found no exact records for gemini-3.5-live-translate-preview, gemini-robotics-er-2-preview, Robotics ER 2, or Live Translate under the relevant graph/adapters areas.
• Existing Gemini graph coverage includes related files such as:
  • packages/atlas/graph/compute/model-families/gemini-3.yaml
  • packages/atlas/graph/compute/models/gemini-3-5-flash.yaml
  • packages/atlas/graph/compute/models/gemini-3-1-flash-live.yaml
  • packages/atlas/graph/compute/models/gemini-3-1-flash-tts.yaml
  • packages/atlas/graph/compute/providers/google.yaml
  • packages/atlas/graph/compute/providers/gcp-vertex.yaml
  • packages/atlas/graph/catalog-meta/evidence-sources/
  • packages/atlas/graph/catalog-meta/claims/
• Adapter/proxy verification touchpoints are packages/adapters/transport/src/engines/google.ts, packages/adapters/proxy/src/adapters_proxy/transports/google.py, and packages/adapters/proxy/src/adapters_proxy/transports/vertex_native.py; current code demonstrates generateContent / streamGenerateContent style support, not specialized Live Translation or robotics-preview behavior.

Affected Components

• Packages: atlas, adapters
• Effort: effort:medium

Recommended Approach

1. Inventory exact normalized IDs before writing files:

   rg -n "gemini-3\.5-live-translate-preview|gemini-robotics-er-2-preview|Robotics ER 2|Live Translate" packages docs .a5c --glob '!node_modules'

2. Reuse any prior Track Google Gemini 3.5 Live Translate Preview #1002 Live Translate work if implementation finds it; otherwise add source-backed graph records for the missing exact model IDs.
3. Add/update model-family, provider serves / model served_by, evidence-source, and claim records together.
4. Use official Google evidence for model code, lifecycle, modalities, context/output limits, pricing, regions, and provider availability. Leave unknown fields unset rather than inheriting from nearby Gemini models.
5. Model transport support carefully. Live Translate and Robotics ER 2 should not be marked as ordinary generateContent compatible unless docs and adapter/proxy tests prove it.
6. Add focused claim tests for high-risk values where practical, then run Atlas graph validation/build checks.

Reproduction

Run:

rg -n "gemini-3\.5-live-translate-preview|gemini-robotics-er-2-preview|Robotics ER 2|Live Translate" packages docs .a5c --glob '!node_modules'

Expected current result before implementation: no exact graph/adapters records for these model IDs. Then inspect packages/atlas/graph/compute/model-families/gemini-3.yaml and provider files for missing has_version / serves edges.

Related Issues/PRs

• Track Google Gemini 3.5 Live Translate Preview #1002 previously tracked gemini-3.5-live-translate-preview; avoid duplicate Live Translate records if any resolved work exists outside the current tree.
• Track Google Gemini 2026 model catalog updates #1465 is a broader closed Gemini 2026 catalog reconciliation issue and includes Live Translate in its catalog snapshot, but does not appear to cover Robotics ER 2 specifically.
• Track Gemini 3.1 Flash Live and TTS model variants #884 tracked Gemini 3.1 Flash Live/TTS variants and is a useful adjacent implementation pattern, not a duplicate.

Priority: medium

This affects Atlas catalog freshness and downstream model/provider discovery, but it is not a production outage, crash, or data-loss issue.

Risk Analysis

• Risk Level: risk:medium
• Partial duplicate with Track Google Gemini 3.5 Live Translate Preview #1002
  • Mitigation: grep exact normalized IDs and inspect prior issue-linked work before adding new records.
• Overstated transport support
  • Mitigation: represent Live API / robotics-preview support as partial or unknown unless verified by official docs and adapter tests.
• Incorrect provider availability
  • Mitigation: add Gemini API, Vertex, Azure, or Bedrock edges only with exact provider-specific evidence.
• Volatile preview metadata
  • Mitigation: source every high-risk claim from current official docs and leave unsupported fields unknown.
• Graph consistency regressions
  • Mitigation: update model, family, provider, evidence, and claims together; run Atlas validation/build checks.

Ready for development.