Evidence
Claim to evidence map for Metriplane.
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.
Archived author-run evidence Captured v0.2.0 values
Table
Every claim has a verification path and a boundary.
| 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. |
| 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 generated 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. |
Primary artifacts
Files to inspect in the archived author-run evidence package.
These paths are archived under evidence/paper_v2_0/ for
inspection. Never use that package as a fresh rerun destination; fresh
replay and Atlas output belong in /tmp/metriplane-softwarex-runs
and /tmp/metriplane-softwarex-atlas.
Artifact
evidence/paper_v2_0/test_output.txt Artifact
evidence/paper_v2_0/logs/deterministic_replay.txt Artifact
evidence/paper_v2_0/logs/atlas_assembly_cell_run.txt Artifact
evidence/paper_v2_0/logs/bundle_verify.txt Artifact
evidence/paper_v2_0/logs/regression_test.json Artifact
evidence/paper_v2_0/atlas_run/cell_truth_report.md Artifact
evidence/paper_v2_0/atlas_run/evidence_bundles/INC-0001.zip Artifact
evidence/paper_v2_0/atlas_run/regression_tests/INC-0001.yaml 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 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 arbitrary anomaly-detection claimNo successful-remediation claimNo production-factory validationNo factory-wide deployment readinessNo complete external-validation claimNo SoftwareX acceptance or peer-reviewed publication claim
Next step
Challenge the evidence map.
The best feedback is concrete: missing source, weak claim, unclear command, or a boundary that should be sharper.