TALOSROBOTICS OPERATIONS

SYSTEM ARCHITECTURE

Three environments, one controlled gateway

The browser is an operations interface—not a hardware controller. The dashboard backend authenticates callers, brokers requests, and forwards authorized operations to platform services.

01 · OPERATORWindows laptop

Dashboard UI and API gateway for status, requests, and audit.

02 · COMPUTEJetson Thor

AI inference, orchestration, robot state, and validated control services.

03 · SIMULATIONUbuntu workstation

Remote Isaac Sim, evaluation, and development workflows.

AI PIPELINE

Model services

The project architecture describes speech recognition, reasoning, speech generation, perception, and motion-generation components as separate services. Model deployment health is reported by the backend, not inferred by this page.

SAFE BY DESIGN

Simulation before hardware

Isaac Sim is the default target. Real-robot operation requires explicit authorization and confirmation, service-side validation, and independent robot safety systems.

The physical emergency stop is independent of the dashboard and all software services.

DEPLOYMENT BOUNDARIES

Modular services

Platform components are independently deployable and communicate through approved APIs over a private network or VPN. Docker Engine, internal secrets, and direct motor interfaces are never exposed to browser code. Isaac Sim and training pipelines run outside the robot-control container.