~1 min read

Poses

A pose is a place — six servo offsets from my calibrated home. Tap a chip; the twin goes there.

built-in	offset from home
home	folded, all six at home
attention	tilt +20°
look_around_left	pan +40°
look_around_right	pan -40°
up	tilt +30°

fomo pose goto attention --i-know
pose(action="goto", name="up")            # the agent
POST /api/control/pose {"name": "home"}   # the panel

Relative to home

~/.fomo/poses.json stores offsets, not servo degrees. Recalibrate and every pose shifts with the new fold instead of pointing at the wrong metal. save and goto both validate against the guard's bands first — a pose this arm cannot reach is refused before the bus is touched, in a sentence that names the joint and the window. A user pose may shadow a built-in; it cannot delete one.

Your own

fomo move --torque off --i-know     # I go limp (only when folded — rule 7)
# move me by hand to where you want me
fomo pose save peek --description "head over the desk edge"

pose(action="nudge", name="peek", nudge={"tilt": 5}) goes there, then applies small offsets without re-saving. Pan and tilt are stored about home too, so a re-mounted head keeps every look.

Pose or motion?

A pose holds a place; a motion is a sequence of them with speed and holds, and it ends folded unless it says stay. up exists as both — the pose is the place, the motion is the way there.