ARCHITECTURE · SOMATIC

CANDIDATE

Translate intent into embodied capability — without leaking hardware details upward.

The Somatic Translator is the candidate hardware-agnostic boundary between approved action semantics and a typed CapabilityPlan.

STATUS BOUNDARY

The v0.1 contract is a baseline, not a final motion planner. It must not emit motor IDs, raw servo ticks, CAN frames or simulator-specific commands.

INPUTS

Intent is interpreted against the actual body.

01

ActionIntent

Explicit model-agnostic action semantics approved for downstream consideration.

02

Self model

The current embodied system and its declared body context.

03

Capability registry

Typed capabilities the body can expose without exposing raw device details.

OUTPUT

The result remains hardware-agnostic.

01Approved ActionIntent
02Self Model + Capabilities
03Somatic Translator
04CapabilityPlan
05Operation Safety Gate
06Body Adapter

WHY THIS BOUNDARY

Motion planning and device control should not collapse into cognition.

A cognition provider may be an LLM, VLM, VLA, deterministic planner or future model. None receives direct actuator authority merely because it produced a high-scoring proposal.

SOURCE MATERIAL