Vehicle documentation¶
Start with Vehicle system architecture for the boundaries between definitions, dealership packages, persistence, customization, previews, and spawned vehicles.
Maintained references¶
- Vehicle car data and persistence is the source of truth for saved vehicle data, migration, quarantine, and compatibility.
- Vehicle customization defines customization values, ownership, pricing, and commit behavior.
- Vehicle asset authoring contracts defines model naming and cross-runtime authoring invariants.
- Vehicle assets documents legacy and assembly-v1 asset shapes, assembly definitions, tags, and runtime locations.
- Dealership package groups documents package schema, resolution, validation, and catalog integration.
- Assembly vehicle tuning documents non-physical DriveSeat overlays and tuning ownership.
- Assembly asset authoring workflow describes the current manual-to-generated workflow for assembly-v1 definitions.
Maintained references describe the current repository. Statements such as "currently" should be checked against their linked runtime locations when behavior changes.
Historical case studies¶
The repository's docs/vehicles/case-studies/ directory records what happened during specific vehicle conversions and generator experiments. These files deliberately preserve the inputs, paths, limitations, and follow-ups that existed at the time. They are evidence for generalizing the vehicle-definition generation process, not descriptions of the current vehicle definitions, so they are not published on this site.
Do not update a case study merely because its vehicle or asset has since changed. Add maintained guidance to the reference documents above, or add a new case study for a later generation run.