VEHICLE LAB / DOCUMENTATION

Scope, evidence & limitations

Software scope

This is a v0.1 release candidate for a reusable engineering notebook. Project creation, geometry import, validation, static inspection and rigid-body replay are implemented. Generic replay currently supports boxes and cylinders; the vehicle example has a separate purpose-built replay adapter.

Engineering scope

No complete vehicle, structural joint design, manufacturing packet or operating release is established. Physical printing, assembly, load tests and driving are not demonstrated by these assets. The RC25 R0 steering issue, R3d fit findings and incomplete current vehicle integration remain open. The R5 body is a body and ergonomics study, not a completed mechanical assembly.

What the visuals mean

Orbiting a mesh establishes that a display loads.
Separating groups explains part relationships; it does not establish a feasible installation path.
Replay applies recorded poses; it does not solve new dynamics.
Source hashes establish byte identity; they do not prove the physical model is correct.
Passing numerical tests establishes the tested equations or program behavior within their stated coverage.

Evolution

The history is a register of authored revisions, reasons and evidence. OpenEvolve, AlphaEvolve or another automatic evolutionary optimization system has not been run as part of the demonstrated pipeline.

Before a physical experiment

Define a bounded experiment, its exact configuration and acceptance criteria. Verify the component interfaces, material assumptions, mechanism behavior and relevant hazards with qualified people and actual measurements. A new study may proceed with a narrow claim without implying that a whole vehicle is ready.

Performance

The full vehicle example includes several million source triangles and tens of megabytes of geometry. It is intended for a capable desktop browser. The website, film and small starter work on smaller screens; smooth interaction with every detailed model is device dependent.