Tagged: architecture

Every guide, note, and policy on YouDuck tagged「architecture」.

• Microduck system architecture

  What each of the seven daemons owns, why the split falls where it does, and how they talk.

• Control plane and data plane

  Every daemon shares one JSON-RPC contract, but sensor streams do not travel over it.

• deadman: why there is no stop button

  A timeout that zeroes velocity when no fresh intent arrives. It is what stops the robot when the pad process dies.

• The 61-dimensional observation contract

  Every policy shares one observation format, which is what lets the runtime hot-swap between walking, recovery and tricks.

• Policy hot-swapping

  Switching between walking, recovery and trick policies at runtime, with no restart and no stop.

• microduck — the robot's own software

  The software that runs on the robot: seven Rust daemons, the robotctl command line, and the update and rollback system.