Skip to main content
The Twin (twin) node reads a digital twin and its assigned controller policy and exposes them as structured outputs. Use it upstream of Fuzzy Matcher so voice pipelines know which command strings are valid for that robot, and to surface controller identity/mode to downstream nodes.
Palette category: Data Sources. Runs on cloud and edge (edge workers resolve the policy via the Cyberwave API).

Inspector

  • Digital Twin — combobox selector.
  • twin_uuid is stored in node parameters, not the generic input-mapping row.

Policy resolution

The node resolves the active policy from:
  1. Twin controller_policy FK, or
  2. twin.metadata.controller_policy_uuid
If neither is set, execution fails with a clear error.

Outputs

control_actuations only includes locomotion slugs (WASD-style). Non-locomotion bindings (lights, camera, take_photo) appear in control_labels but not in control_actuations.

Fuzzy Matcher wiring

Execution targets