Four layers, one narrow product promise

RoboTunnel has a broader internal architecture than the current public positioning. The current public promise is narrow, but the architecture still helps explain where CLI, Discord, platform, and the robot-side agent fit.

Layer model

  • Interaction: CLI and Discord
  • Platform: auth, routing, signaling, relay orchestration
  • Connection: WebRTC/TCP transport selection and session establishment
  • Application: robot-side agent skills and Debug Projection runtime

Robot-side agent

The open-source agent is where visual_debug, ros2_observe, host_debug, and monitor live. It is also where the local trust boundary exists for robot-side execution and provider keys. See Skills for the first-touch capability map.

Interfaces

CLI is the primary interface for developers. Discord is the secondary interface for teams and operators. Both route into the same platform and robot-side capability model, but not every interaction is symmetric.