Section 1Product Foundation
Requirement language
Defines normative requirement terms, priorities, program tiers, and verification methods.
Section relationships
- SHALL is mandatory for the stated release priority.
- SHOULD is expected unless a documented design decision explains why not.
- MAY is optional.
- Each requirement is intended to be atomic, named, traceable, and independently verifiable.
- Architecture choices such as a particular UI framework are not requirements unless the choice constrains product behavior.
Priorities
| Priority | Meaning |
|---|---|
| MVP | Required for the useful, portable, Rust-only outdoor-rover pilot. |
| Beta | Required before the platform is offered as a general robotics beta. |
| Future | Part of the long-term multiphysics vision, but not committed to the MVP or beta schedule. |
| External | Conditional conformance requirement for the Engineering Integration Profile; never required by the portable Rust-only distribution. |
MVP and Beta are delivery commitments. Future rows reserve named capability boundaries but are not commitments until reprioritized. External rows are also conditional: an optional integration is not promised merely because it is listed, but if that integration is delivered, every applicable SHALL statement governs it. Future MAY rows are tracked roadmap candidates rather than accepted requirements.
The program tiers are named as follows:
| Program tier | Scope |
|---|---|
| Portable MVP | The useful Rust-only outdoor-rover product defined in section 30. |
| General Robotics Beta | The portable product expanded for multiple robot classes, richer sensors, extensions, calibration, and batched experiments. |
| Engineering Integration Profile | Optional ROS 2, FMI, HIL, CAD, SPICE, firmware-emulation, and external-solver adapters. |
| Research Horizon | Future deformable, structural, fluid, granular, failure, and other specialist multiphysics capabilities. |
Verification methods
| Method | Meaning |
|---|---|
| Test | Automated or repeatable executable verification. |
| Analysis | Numerical, convergence, benchmark, or evidence-based evaluation. |
| Inspection | Review of source, schema, manifest, report, or configuration. |
| Demonstration | End-to-end user workflow performed against acceptance criteria. |
Generated from the canonical specification. Edit section metadata or prose in docs/requirements.md; the website rebuilds this page and its relationships automatically.