How it works
Evaluate the candidate before hardware validation.
Synexis evaluates candidate action traces against controller constraints and prior release evidence, then localises findings for engineering review.
Evaluation flow
A versioned evidence chain.
01
Candidate action trace
Versioned policy outputs, timestamps, units, and run identifiers.
02
Controller profile
Declared joint ordering, kinematic limits, timing, and interface constraints.
03
Release comparison
Candidate behaviour compared with a trusted baseline when one is available.
04
Deployment evidence
Localised discontinuities, constraint findings, regressions, and review status.
Evidence output
Findings localised to the release.
- 01
Policy–controller compatibility
Evaluate the candidate trace against the target controller profile.
- 02
Instability localisation
Trace anomalous behaviour to a specific run and execution interval.
- 03
Constraint analysis
Flag proximity to or excursions beyond declared limits.
- 04
Release regression
Identify candidate behaviour that diverges from the trusted baseline.
Evaluation input