Release and citation
GitHub release v0.2.0, its tag commit, the Zenodo DOI, MIT license, and citation metadata identify the artifact.
SoftwareX manuscript
v0.2.0 as a bounded research-software artifact.
Metriplane v0.2.0 is the DOI-archived public release and primary software artifact for the planned SoftwareX submission. This website does not claim SoftwareX acceptance or peer-reviewed publication.
Release tag: v0.2.0 Tag commit: 8e35ed5bb20837f7dc46354777407b848d7ce17a Evidence capture commit: 44bed6d85786675c5581154f588a7ad2529c85d6 DOI: 10.5281/zenodo.20736619 Archived author-run evidence: evidence/paper_v2_0/ Archived author-run gate: 580 passed Reviewer path
What a reviewer can inspect and reproduce.
Core reproduction
The camera-free, replay-based, observe-only path uses the exact tag and writes fresh output only under /tmp.
Archived evidence
Captured logs, the Cell Truth Report, bundle, regression YAML, and checksums in evidence/paper_v2_0/ are author-run evidence for inspection.
Manuscript relevance
The manuscript artifact centers on a bounded workflow.
The claim is not that Metriplane controls industrial hardware or validates a production factory. It is that a replayed workcell incident can become an inspectable evidence bundle, be verified locally, and be preserved as a generated regression check.
replayed/calibrated state
-> physical event ledger
-> INC-0001 incident
-> Cell Truth Report
-> evidence bundle
-> local verification
-> generated regression checkValidation paths
Core reproduction and the maintainer gate are separate.
Core reproduction
The exact v0.2.0 workflow uses temporary paths, requires no
Playwright, Chromium, Docker, ROS 2, or camera, and does not overwrite
evidence/paper_v2_0/. The public independent core workflow passed.
Optional full maintainer gate
The optional gate requires additional browser and system dependencies.
580 passed is archived author-run release evidence. The
public independent macOS gate recorded
575 passed, 3 skipped, 2 failed, so the public full suite
is not a complete pass.
Evidence
Claims that matter for manuscript review.
| Claim | Evidence | How to verify | Boundary |
|---|---|---|---|
| v0.2.0 is archived as a public release | GitHub release and Zenodo DOI 10.5281/zenodo.20736619 | Open the v0.2.0 release and Zenodo record. | SoftwareX acceptance or peer review is not claimed. |
| The archived author-run maintainer gate recorded 580 passed | Archived author-run evidence/paper_v2_0/test_output.txt reports 580 passed. | Inspect the archived file; do not use evidence/paper_v2_0/ as a fresh rerun destination. | The public independent macOS gate recorded 575 passed, 3 skipped, 2 failed; the public full suite is not a complete pass. |
| The camera-free replay is deterministic | deterministic_replay.txt reports pass=true, 0.0 cm position difference, and 0 event mismatches. | Run with RUNS=/tmp/metriplane-softwarex-runs and the checked-in demo session. | Checked-in demo session only; no live-camera claim. |
| The assembly-cell replay produces one incident | atlas_assembly_cell_run.txt reports 6 physical events, 1 process deviation, and 1 incident. | Run metriplane atlas run with the assembly_cell domain pack and --out /tmp/metriplane-softwarex-atlas. | One deterministic assembly-cell domain pack and replay. |
| INC-0001 is explainable as a Cell Truth Report | cell_truth_report.md records a 35.0 s wait for torque_driver_1. | Inspect archived evidence/paper_v2_0/atlas_run/cell_truth_report.md. | Derived from replayed planar state, not raw-video judgement. |
| The incident is packaged as portable evidence | INC-0001.zip contains manifest, checksums, incident, timeline, report, and replay command. | Inspect artifacts/INC-0001_zip_listing.txt and the bundle manifest. | Local content/checksum verification; not malware scanning. |
Limitations
Manuscript readiness includes saying what is not proven.
The artifact is observe-only research software for a bounded, planar/tagged-asset workcell. It does not claim robot or machine control, safety certification, quality approval, successful remediation, arbitrary anomaly detection, marker-free tracking, full 3D reconstruction, production-factory validation, or complete external validation.
Next step
Review the artifact against the SoftwareX manuscript.
The useful question is whether the release, archived evidence, fresh core workflow, maintainer gate, and limitations are clearly separated.