Portable MVP definition and acceptance gates
Defines the distributable reference rover scenario, required models and workflows, qualification evidence, and release gates for the first useful product.
Section relationships
The BeforeMetal Portable MVP is a local, Rust-only, headless-capable simulator with a basic viewer for an outdoor rigid-link rover. It imports a documented URDF and SDFormat subset; models rigid mechanics, gravity, terrain, wind and gusts, approximate rain and wetness, materials, motors, gearing, battery, encoders, IMU, and range sensing; executes a trusted native Rust controller; runs finite parameter sweeps; and produces comparable results with fidelity metadata and declared reproduction modes.
The MVP does not require Python, ROS 2, MuJoCo, Gazebo, FMI, ngspice, CAD, CFD, FEA, photorealism, or a discrete GPU.
The reference baseline is defined around a versioned rover, world, scenario, benchmark fixtures, and required evidence that can be distributed or reproducibly obtained without access to a physical rover. Optional published, manufacturer, community, independent-reference, or physical datasets may be imported to strengthen named claims, and their provenance and evidence class remain visible.
| ID | Name | Priority | Requirement | Verification |
|---|---|---|---|---|
| ACCEPT-001 | Reference benchmark approved | MVP | The product definition SHALL name the distributable rover model, mission, environment, design variables, observables, success criteria, evidence-qualification procedure, and policy for disclosing unavailable independent evidence. | Inspection |
| ACCEPT-002 | Pure-Rust installation | MVP | A clean supported machine SHALL install and execute the complete reference workflow without mandatory non-Rust native solver libraries. | Demonstration |
| ACCEPT-003 | Import-to-result workflow | MVP | A clean installation SHALL import the reference robot and world, compile, run, inspect, export, input-re-execute, and play back a result. | Demonstration |
| ACCEPT-004 | Design comparison workflow | MVP | A user SHALL compare at least two modeled hardware configurations using identical mission, seeds, metrics, and fidelity settings. | Demonstration |
| ACCEPT-005 | Controller comparison workflow | MVP | A user SHALL compare at least two native Rust controller configurations using identical robot and environment conditions. | Demonstration |
| ACCEPT-006 | Weather workflow | MVP | The reference experiment SHALL compare at least dry, wet, calm, and gust conditions using documented approximations. | Demonstration |
| ACCEPT-007 | Fault workflow | MVP | The reference experiment SHALL exercise at least one sensor and one actuator or power fault with visible causal diagnostics. | Demonstration |
| ACCEPT-008 | Analytical qualification | MVP | All approved MVP analytical, mechanics, device, sensor, timing, and import benchmarks SHALL pass their approved criteria. | Analysis |
| ACCEPT-009 | Numerical convergence | MVP | The reference observables SHALL satisfy their approved timestep and solver-setting convergence criteria. | Analysis |
| ACCEPT-010 | Reproducibility | MVP | The reference deterministic runs SHALL satisfy TBD-REPRO-CRITERION. | Test |
| ACCEPT-011 | Performance | MVP | The reference workflows SHALL satisfy all resolved MVP performance budgets. | Analysis |
| ACCEPT-012 | Endurance | MVP | The reference endurance workload SHALL satisfy TBD-REL-ENDURANCE. | Analysis |
| ACCEPT-013 | Reference evidence status | MVP | Every reference capability SHALL publish its applicable evidence source classes or their absence and its qualification status, including an explicit unqualified status when no applicable independent evidence exists. | Inspection |
| ACCEPT-014 | Independent decision-ranking evidence | Beta | A release claiming externally validated design ranking SHALL rank the agreed alternatives consistently with a versioned independent comparative dataset that was not used to select, tune, or threshold the ranking rule. | Analysis |
| ACCEPT-015 | Actionable limitation report | MVP | The completed reference run SHALL identify engineering-property transformations and dispositions, inactive engineering properties, inactive or unsupported effects, material approximations, unavailable evidence, and out-of-envelope conditions in one fidelity card. | Inspection |
| ACCEPT-016 | Independent quickstart | MVP | A user unfamiliar with the codebase SHALL complete the quickstart without direct developer intervention. | Demonstration |
| ACCEPT-017 | Security baseline | MVP | The release candidate SHALL have no unaccepted critical or high-severity vulnerability under the approved policy. | Inspection |
| ACCEPT-018 | Beta extension gate | Beta | An external contributor SHALL implement and package one conforming extension without modifying core crates. | Demonstration |
| ACCEPT-019 | Backend-independence gate | Beta | A second mechanics implementation or purpose-built conformance backend SHALL compile the shared reference model and pass the contract suite without introducing its native types into canonical project data. | Analysis |
| ACCEPT-020 | Beta co-simulation gate | External | The FMI adapter SHALL pass applicable standard reference tests and BeforeMetal multi-rate coupling tests. | Analysis |
| ACCEPT-021 | MVP decision closure | MVP | Every TBD-* value referenced by an MVP requirement SHALL be approved or the dependent requirement SHALL be explicitly reprioritized before MVP implementation is declared complete. | Inspection |
| ACCEPT-022 | Independent pilot workflow | Beta | TBD-PILOT-COUNT independent roboticists or teams SHALL complete the reference design-decision workflow within TBD-PILOT-TIME and TBD-PILOT-HELP, with the selected decision and product limitations recorded. | Demonstration |
| ACCEPT-023 | Physical-asset-independent workflow | MVP | A clean supported machine SHALL complete the reference import, compile, run, inspect, export, input-re-execution, playback, sweep, and comparison workflow without a physical robot, measurement hardware, or user-conducted physical test. | Demonstration |
| ACCEPT-024 | Portable runtime-action gate | Beta | A clean portable installation SHALL execute a versioned fixture covering accepted and rejected entity-lifecycle, constrained state-override, disturbance or fault, and controller-restart actions and SHALL verify deterministic ordering, atomic failure, request receipts, and causal-journal evidence without an external runtime. | Test |
| ACCEPT-025 | User regression gate | Beta | A clean portable installation SHALL execute TBD-BETA-REGRESSION-SUITE headlessly, emit the specified machine-readable summary and process statuses, pass the accepted cases, and detect the versioned intentional divergence. | Test |
| ACCEPT-026 | Dynamic-analysis gate | Beta | The portable General Robotics Beta profile SHALL pass the reference cases and criteria approved under TBD-VAL-DYNAMIC-ANALYSIS. | Analysis |
| ACCEPT-027 | Beta decision closure | Beta | Every TBD-* value referenced by a Beta requirement or acceptance gate SHALL be approved or the dependent requirement SHALL be explicitly reprioritized before General Robotics Beta is declared complete. | Inspection |
Change rationale (ACCEPT-001, ACCEPT-004, ACCEPT-013, ACCEPT-014, ACCEPT-023): The previous baseline conflated delivery of an engineering simulator with a team-run physical qualification campaign. ADR-0001 makes the distributable digital reference scenario, analytical and numerical qualification, convergence, reproducibility, and explicit evidence status sufficient for MVP. Optional independent datasets can strengthen named claims, but their absence produces an honest unqualified status instead of blocking simulation. Externally validated design ranking moves to Beta because it depends on a suitable independent comparative dataset.
Change rationale (ACCEPT-024–ACCEPT-027): The new v0.4 Beta commitments need end-to-end gates rather than only isolated schema checks. The fixtures remain portable, offline, and physical-asset independent; the separate decision-closure gate prevents unresolved Beta criteria from being treated as accepted values without changing the Portable MVP gates.
Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.