Evaluation
Design in. Evidence out.
Synexis lands with paid technical evaluations — not a grand “robot brain.” The evaluation packet is the wedge: concrete artifacts and honest limits.
The process
01
Upload a hand design
Share the morphology information Synexis needs to build a graph — joints, actuators, couplings and the constraints that matter for safe control.
02
Projection & stress
We run the deterministic projector against proposed actions, collect failure modes, and assemble telemetry into a coherent engineering packet.
03
Packet delivery (~2 weeks)
You receive bounded, safe commands, failure data, an engineering report, and an explicit statement of what has and hasn't been proven.
What you get back
- Bounded, safe command sets for the submitted morphology
- Failure data from projection stress cases
- An engineering report written for control-systems readers
- An explicit claim-boundary statement — what is proven, and what is not
Claim boundary — ships with every packet
We don't claim physical-hardware performance we haven't measured. Each evaluation states exactly which results are simulation-backed, which are reference SDK paths, and which remain targets. Trust is the product.
Evaluation → Pilot → Runtime