Field · robotics

Robotics.

Robotics is the work of making physical systems move, sense, and act with control. It brings together mechanisms, kinematics, actuation, geometry, collision, constraints, timing, and validation — the place where software representations meet bodies, motors, instruments, and space.

Here, robotics connects geometric reasoning, complex software, and the instrument work at NaadLabs behind the Harmonic Sitar.

Robotics mark A simple kinematic chain: four joints connected by links, traced from a fixed base on the lower left to a free end-effector at upper right. BASE END
FIG · kinematic chain
Physical focusMotion / mechanisms
Builds onGeometric reasoning
ContextNaadLabs / Harmonic Sitar

Definition

What "robotics" means here.
Robotics

Robotics is the field of physical systems that move, sense, and act. Here it includes mechanisms, kinematics, actuation, geometry, collision checking, constraints, control, timing, and validation. The central question is how a system should be represented so a physical action can be planned, checked, controlled, and trusted.

Robotics is closely related to geometric reasoning, but they are different things. Geometric reasoning is the mathematics of shape and space; robotics is where that mathematics meets motors, mechanisms, instruments, and real physical consequences.

At a glance
Builds on
Geometric Reasoning
Lab context
NaadLabs
Music-tech example
Harmonic Sitar
Related field
Music Technology

Why it matters

Physical systems turn representation errors into real-world failures.

A wrong representation can move the wrong body.

Robots act in physical space. If the representation is wrong, a software error can become a collision, missed motion, unstable control loop, or unsafe physical state.

Different questions need different maps.

Reachability, collision, smoothness, timing, safety, control, and validation are not the same question. Each needs a representation that exposes the right structure.

AI alone is not a robotics architecture.

Learning systems can help at the boundary, but physical reasoning still needs structured representations for geometry, constraints, control, and validation.

Approach

Treat robotics as representation design for physical questions.

Yoav's approach to robotics starts with the question being asked. A robot is many maps at once: joint states, coordinate frames, geometry, collision volumes, trajectories, constraints, control signals, timing assumptions, and validation records. Each map answers a different physical question.

The work is to choose the right representation for the task: frames for position and orientation, geometry for shape, collision volumes for contact risk, configuration spaces for reachability, constraints for allowed motion, trajectories for timing, and control signals for actuation. Geometric reasoning is the mathematics that makes many of these questions checkable.

For complex robotics software, Clause matters here too: it keeps requirements, design notes, code and tests connected as robotics software changes. Robotics makes that need concrete, because software decisions eventually meet physical motion.

NaadLabs and the Harmonic Sitar give this robotics work a musical body: robotics applied to instrument R&D, performer-centered augmentation, resonance, and playable physical systems.

Stance
  • The right map depends on the question.
  • Physical reasoning needs structured representations.
  • Geometry, control, and validation stay connected.