Technology
Morphology in. Safe commands out.
Synexis is simulation-first today. This page separates the reference SDK path from what has been proven on physical hardware — which we do not overclaim.
The morphology graph
A robotic hand is represented not as a flat list of numbers but as a morphology graph: nodes are joints, actuators, tactile sites, palm regions and tendon anchors; edges are the kinematic links, actuator mappings, tendon couplings, tactile-contact relations and safety constraints between them.
Adding a new hand becomes writing a new morphology profile — not rewriting the control stack.
Architecture
Planner → projector → hand. Synexis sits beneath existing planners.
01
Planner / policy
Any upstream planner or learned policy proposes an action. Synexis does not replace it.
02
Constraint projector
A deterministic projector maps the proposal into the feasible set defined by the hand's morphology graph.
03
Hand hardware
Commands that are mechanically valid and safe for that specific hand — designed for sub-millisecond local control.
What exists today
Honest current implementation — reference SDK path and simulation evidence, not physical-hardware performance claims.
SDK runtime path
Reference path for integrating the projector beneath an existing planner. Local, no cloud dependency.
Canonical 21-joint profile
A shared morphology baseline used to develop and exercise the graph representation.
Shadow-style draft graph
A morphology graph drafted in the style of a Shadow-like dexterous hand — joints, actuators, couplings and constraints.
Local telemetry & benchmark packets
Evaluation artifacts returned with bounded commands, failure data and an explicit claim boundary.
MuJoCo Shadow-Hand smoke adapter
Loads and steps the public MuJoCo Shadow Hand model; graph commands mapped to actuators. A simulation smoke test — not a physical-hardware result.
We publish claim boundaries on every evaluation. See Evaluation or write to contact@synexis.ltd.