Know what your robots physically did, and prove it.

Identify contact and impact events from the video, force, and logs you already record, with evidence attached.

haptica · run 0042local
00:08.70contact2 sensors · Vision Sensor + force thresholdHigh
00:12.41impact1 sensor · force thresholdHigh
00:17.05contact1 sensor · Vision SensorMedium
00:21.30unknownabstained · preservedUnknown
Confidence band, never a decimalsuggested region, not point
Evidence window · blue contact · pink impact
The record

One record of what physically happened.

01

Connect the run

Robot video, force, robot state, logs, and audio on one timeline.

02

Review contact and impact

Detections aggregate into one event per moment. The record states how it was found.

03

Share the evidence

Every event links its evidence: the source windows, the confidence band, and which sensors said so.

Review Room mid-review: two synced cameras over the rig, the loop transport with a plus-minus 1.5 second pad, the force strip with event spans, and the events ledger, each contact event carrying a Medium band, one wrist sensor, and a force-settled end basis
Review Room · real capture, uncalibrated run (bands capped at Medium)Camera footage: RH20T (CC-BY)
Jobs

What teams do with the record

Fleet event search: the query "show me every hard impact" compiled to filters, five reviewed impact matches, each with a High confidence band, and the evidence panel with its onset grid
Fleet event search · real capturePlayback footage: RH20T (CC-BY)

Exception triage

Alert to reviewed event, no engineer rebuilding the timeline. Evidence attached.

Safety and behavior review

Every contact and impact across the fleet lands in one queue, under one schema.

Fleet search and regression

Query every contact and impact across runs. Did rates move run over run? Ask the ledger.

Training-data curation

Accepted events are labeled examples with provenance. Export the set your model needs.

Open source

Start with Haptica Core.

The open app, schema, and review workflow.

  • Local-first Review Room for robot runs
  • Open contact and impact event schema (physical-events v0.3)
  • Manual, rule, threshold, acoustic, and plugin sensors
Production

Add the platform when it matters.

Where the event is visible but not directly sensed.

  • Haptica Vision Sensor for video contact and impact
  • Edge runtime and deployment calibration
  • Evidence retention, controls, and support
Standards

Built to sit inside the stack you have.

Schemaphysical-events v0.3 · open schema, validators, typed SDKs
MCAPRides inside MCAP as a channel convention
LeRobotEpisode adapter for public datasets
Data rightsPrivate by default · contributor mode is explicit

Start with one run.

Connect a source and get contact and impact events. If open core covers you, stay there. If you need production detection, add the platform.