Posture sensing is for context recognition, not command input
Aliases: postural context · activity recognition · sit-stand-walk
What it is
Chair-back angle, trunk inclination, and sit / stand / walk from posture sensing describe the bodily situation a person is in, not a confirm / cancel command. Treat that stream as a gesture vocabulary and every shift for comfort becomes a false trigger. Posture is fit to supply context so that some other channel can issue instructions.
Why it happens
Posture changes infrequently and for mixed reasons. People shift to unload fatigue, reach, or turn to speak; the kinematics are not a minimal action set prepared for a machine. Inertial sensors and pressure mats see gravity relative to body axes and pressure on a support surface. Classifiers can separate coarse states (sit, stand, lie, walk); they cannot separate “intend to pause playback.” Writing a posture threshold as a command creates a bodily Midas problem: the postural edits that living requires are treated as input. Contextual use inverts that: posture only changes how other signals are read—down-weighting electrodermal inference while walking, or enlarging type when the user stands.
Studying it
The standard activity set is sit, stand, walk, lie, stairs, from waist, chest, or seat sensors. Factors: sensor site, class granularity, and whether people know they are “issuing commands.” Outcomes: state accuracy, and false-trigger rate when posture is treated as a command (unintended fires per hour). The important contrast is cost asymmetry on the same sensors: a missed context label is often tolerable; a command false trigger is not. Laboratory “standard sitting” undercounts the fidgeting of real desks.
Where it stops holding
In rehab or accessibility, a deliberately designed trunk switch (lean to confirm) can be a command: that is a learned replacement channel, not background recognition of everyday posture. Full-body skeleton tracking used for mid-air gestures has its own onset/offset rules and should not be lumped with seat-pressure context labels. Lying down with a phone is a legitimate context; coding “supine” as power-off punishes bed use. Driving and surgery constrain posture more tightly, so the context classes themselves shrink and an office model will not transfer.
Applying it
- Use posture to retune mode weights, type size, or timeouts—not to bind delete, send, or pay.
- If a trunk command is truly required, make it cross a clear dead zone, keep it reversible, and calibrate it apart from everyday shifting.
- Hold the previous context when state is uncertain; do not flicker modes on the sit/stand boundary.
- Verify by recording natural office or commute motion that the user does not know is being treated as input, and count how many posture changes would have fired if bound to a command.