Inputs
Replay sessions or calibrated planar state streams representing tracked workcell assets.
Technical scope
Metriplane works with replayed or calibrated planar workcell state. It turns state into events, incidents, reports, bundles, verification targets, and generated regression checks. The software is camera-compatible for calibrated input, while the public reproduction path is camera-free and replay-based.
input:
replayed/calibrated planar state
domain:
bounded workcell
output:
evidence and generated checks
control:
none Architecture
Components
Replay sessions or calibrated planar state streams representing tracked workcell assets.
Assembly-cell assets, process steps, contracts, work orders, and workspace configuration.
Physical events and process deviations generated from the replayed state and domain pack.
INC-0001 captures the missing required asset, related events, timing, severity, and limitations.
Manifest, checksums, incident JSON, event timeline, report, replay command, and scoped excerpts.
A generated YAML check replays the bounded expectation that the missing tool caused the delay.
Boundaries
The project is research software for evidence review. Its credibility comes from bounded claims, local reproduction, and explicit limits.
Integration posture
The Metriplane repository includes integration surfaces for ROS 2, Omniverse, dashboards, exporters, and local operator review. The public release evidence claim stays centered on the camera-free, local, assembly-cell reproduction path unless separate runtime evidence is linked.
Next step
Questions about exact scope, data assumptions, and verification behavior are the best way to harden the artifact.