What Haptica does, exactly.
We label contact state. Whether physical contact is present and for how long, with confidence and abstention when the video does not support a read. Haptica does not estimate force magnitude.
We find physical-state transitions. Onset and release neighborhoods and sustained contact, where the specific profile passes its event-level gate. Haptica preserves source-provided outcome labels with attribution. It does not infer jams, slips, misalignment, or failed attempts from video.
We label recordings. Haptica runs after the fact and does not sit in the control loop.
We report confidence and abstention. When the video does not support a label, the event is marked as abstained.
We publish results with their scope. Simulation results are labeled as simulation. We will publish the real-robot result whether it passes or fails.
Common questions
What does Haptica label?
Contact state, plus profile-qualified transitions where validated.
Do I need force sensors?
No permanent runtime hardware is required. Private commissioning may use qualified native telemetry or temporary reference sensing to establish and validate the profile.
What do I receive?
A physical-state sequence, a physical-event record, splits, quality and coverage measurements, provenance, the baseline comparison, and integration instructions.
Where does my data go?
Pilots can run in your environment. Retention and deletion terms are set in the engagement agreement.
How do I try it?
Send one hour or complete the pilot brief.