Rust-native robotics simulation
Design. Test.
Decide.
Before Metal.
Design robots, run reproducible experiments, and see every model's evidence status, validity limits, and unqualified gaps.
- 01 Reproducibility specified
- 02 Rust-owned core
- 03 Evidence-aware
The decision loop
From model to evidence.
BeforeMetal treats simulation as a traceable engineering argument—not a black box that emits an authoritative-looking animation.
- 01
Describe
Robot, world, controller, mission, and design variables.
- 02
Compile
Capabilities, timing, ports, fidelity, and unsupported features.
- 03
Run
A reproducible experiment with explicit models and seeds.
- 04
Compare
Hardware, controllers, weather, faults, and parameter sweeps.
- 05
Validate
Compare predictions with available evidence and disclose gaps and validity limits.
System architecture
One platform. Explicit boundaries.
The specification separates models, execution, evidence, integrations, and delivery so each subsystem can evolve without smuggling assumptions into project data.
Explore dependenciesEvidence contract
Know what produced the result.
BeforeMetal is designed to preserve the configuration, assumptions, runtime record, and available comparison evidence—or its explicit absence—behind each engineering decision.
Inspect the evidence requirements- DATA-001 Run manifest
What ran
A manifest records the project, compiled scenario, controller, software, seeds, execution mode, fidelity, and termination state.
- VAL-001 Fidelity card
What it assumed
A fidelity card lists active models, property dispositions, approximations, validity warnings, and available evidence or its explicit absence.
- SYS-011 Run diagnostics
What happened
Simulated time, wall time, real-time factor, solver diagnostics, warnings, and termination reason stay visible.
- DATA-013 Difference report
What changed
A comparison report identifies configuration, software, seed, fidelity, and selected metric differences between runs.
Portable MVP
A rover. Weather approximations. A bounded promise.
The first useful product is a local, Rust-only simulator for an outdoor rigid-link rover with a basic viewer and a complete headless workflow that requires no physical robot or measurement hardware.
Read the MVP definitionIn the portable baseline
- Rigid mechanics, gravity, terrain, wind, and gusts
- Approximate rain, wetness, and surface effects
- Motors, gearing, batteries, sensors, and faults
- Rust controllers, sweeps, results, and fidelity cards
- Digital benchmark qualification without a physical robot
Not required for MVP
- Python, ROS 2, MuJoCo, Gazebo, or FMI
- Production CFD, FEA, SPICE, or CAD
- Photorealism or a discrete GPU
- A claim of universal physical accuracy or certification
Definition before implementation