Technical note
ROS bags, logs, traces, and the next layer of workcell incident evidence.
Robotics teams already use recorded sensor data, ROS bags, logs, traces, dashboards, and simulation replays when investigating incidents. Metriplane does not try to replace those artifacts. It explores what can happen after raw evidence has enough structure to be replayed and reviewed.
Raw evidence is necessary, but often workflow-specific.
A ROS bag or log archive can capture important details: topics, timestamps, state messages, commands, warnings, and sensor streams. That raw evidence is valuable because it preserves the context needed for later debugging. The challenge is that raw evidence usually needs local knowledge before another reviewer can answer simple questions: what happened, which step was delayed, which asset was missing, and what should become a regression check.
Metriplane formalizes a structured evidence layer.
In the assembly-cell demo, replayed workcell state becomes a physical event ledger. A missing torque driver delays a process step by 35.0 seconds. Metriplane then generates incident INC-0001, a Cell Truth Report, an evidence bundle, a bundle verification result, and a generated regression test.
raw/replayed state
-> physical event timeline
-> incident context
-> evidence bundle
-> local verification
-> generated regression testWhy bundles and regression tests matter.
Incident evidence is more useful when it can travel with a manifest, checksums, a human-readable report, and a command that lets another reviewer verify the artifact. It becomes more useful again when the incident can be turned into a regression test that protects against losing the behavior during future development.
What this does not prove.
The release artifact demonstrates this workflow on a deterministic, camera-free assembly-cell replay. It does not claim production-factory validation, robot control, safety certification, full 3D reconstruction, marker-free tracking, or quality-release approval.
How to inspect it.
Start with the 3-minute demo, then run the camera-free reproduction path and compare the output against the evidence table. If something is unclear or weak, leave a comment on Issue #6.