A controller avatar is an Hdl value that carries a controller’s identity for later operations. Instead of passing a controller-name string to every action, setup supplies a Controller value to the continuation that follows it. section 5.2.2
This changes the script’s shape from a flat list of loosely related commands into a dependency-aware tree. RegisterComponent receives the controller avatar, so registration appears only after SetupController has produced it.
Passing the avatar through a script
SetupController creates lCtrl, then registration and sensor reading use lCtrl directly. A second setup similarly creates rCtrl, keeping each controller reference tied to its continuation.
