Metriplane

Technical scope

Observe-only physical observability for bounded workcells.

Metriplane works with replayed or calibrated planar workcell state. It turns state into events, incidents, reports, bundles, verification targets, and regression tests. 

input:
  replayed/calibrated planar state
domain:
  bounded workcell
output:
  evidence and regression artifacts
control:
  none

Architecture

The pipeline is intentionally narrow.

  1. 01 replayed workcell state
  2. 02 physical event
  3. 03 incident
  4. 04 evidence bundle
  5. 05 verification
  6. 06 generated regression test

Components

Major technical surfaces.

Inputs

Replay sessions or calibrated planar state streams representing tracked workcell assets.

Domain packs

Assembly-cell assets, process steps, contracts, work orders, and workspace configuration.

Event ledger

Physical events and process deviations generated from the replayed state and domain pack.

Incident model

INC-0001 captures the missing required asset, related events, timing, severity, and limitations.

Evidence bundle

Manifest, checksums, incident JSON, event timeline, report, replay command, and scoped excerpts.

Regression test

A generated YAML test replays the expectation that the missing tool caused the delay.

Boundaries

Non-claims are part of the design.

The project is research software for evidence review. Its credibility comes from bounded claims, local reproduction, and explicit limits.

Observe-only Planar/tagged-asset scoped Camera-free replay path No robot or machine controlNo safety certificationNo quality-release approvalNo people recognitionNo marker-free tracking claimNo full 3D reconstruction claimNo production-factory validationNo factory-wide deployment readiness

Integration posture

Adapters exist, but runtime claims stay bounded.

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.

Metriplane project visual showing coordinate-plane tracking
Real project visual from the Metriplane repository documentation.

Next step

Point technical questions at the boundaries.

Questions about exact scope, data assumptions, and verification behavior are the best way to harden the artifact.

Give 2-minute feedback Comment on Issue #6 Open GitHub