Archived missing-tool case · v0.2.0

Every claim.
Open to inspection.

This page maps public claims to archived author-run evidence and a separate fresh reproduction path. Each claim has a concrete inspection or verification path and a narrow boundary. The current v0.4.1 PyPI package is a later delivery release and is not substituted for the frozen evidence version.

v0.2.0 / Frozen research artifactDOI 10.5281/zenodo.20736619 ↗

Primary artifacts

The record, file by file.

Read the frozen release files, or save byte-verified copies from the DOI archive. Original paths and checksums are available with every file.

8 saved files
Frozen version and reproduction boundaries

The files are preserved under evidence/paper_v2_0/ in release commit 8e35ed5bb20837f7dc46354777407b848d7ce17a. Copies here match the DOI archive and its SHA-256 checksums.

Keep that archive unchanged. Fresh replay and Atlas output belong in /tmp/metriplane-softwarex-runs and /tmp/metriplane-softwarex-atlas. Follow the reproduction guide.

Table

Every claim has a verification path and a boundary.

Open the claim-by-claim evidence map
Claim Evidence How to verify Boundary
v0.2.0 is archived as a public research release GitHub release and Zenodo DOI 10.5281/zenodo.20736619 Open the exact v0.2.0 release and Zenodo record. v0.4.1 is the current installable software release; 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 has a readable Incident 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.
The evidence bundle verifies bundle_verify.txt reports JSON with pass=true and no errors. Run metriplane atlas bundle verify /tmp/metriplane-softwarex-atlas/evidence_bundles/INC-0001.zip. Verifies this bundle schema/content locally.
The incident becomes a repeatable regression check regression_test.json reports pass=true for missing_tool_caused_delay_INC-0001. Run metriplane atlas test /tmp/metriplane-softwarex-atlas/regression_tests/INC-0001.yaml --json. The generated check covers this incident expectation only.
The project is observe-only and bounded release claim boundaries, Atlas docs, and explicit non-claims. Read docs/release_v0_2_claims.md and docs/atlas/README.md. No robot control, safety certification, quality approval, marker-free tracking, or production validation.

Boundaries

The evidence is useful because the claims are narrow.

The release package demonstrates a bounded, reproducible workflow for a replayed assembly-cell incident. It does not claim a production factory deployment or a safety-certified decision system.

Observe-only

Inspect what happened. MetriPlane does not control the machine.

A bounded workcell

Planar state from tracked or tagged assets, with explicit process rules.

Replay first

A camera-free reproduction path. Integration claims require their own evidence.

Full scope and limitations
  • No robot or machine control
  • No safety certification
  • No quality-release approval
  • No people recognition
  • No marker-free tracking claim
  • No full 3D reconstruction claim
  • No arbitrary anomaly-detection claim
  • No successful-remediation claim
  • No production-factory validation
  • No factory-wide deployment readiness
  • No complete external-validation claim
  • No SoftwareX acceptance or peer-reviewed publication claim

Next step

Reproduce the archived case.

Run the exact v0.2.0 source workflow and compare fresh results with the preserved evidence.