Rensselaer developer documentation

These documents describe the vehicle assembly and package-authoring systems on the repository's dev branch. They are intended for vehicle developers preparing assets, assembly definitions, tuning, customization options, and dealership packages.

Start here

1. Read the vehicle documentation overview for a map of the maintained references.
2. Follow the assembly asset authoring workflow to inspect an asset and produce the definition files.
3. Use vehicle assets for the complete assembly-v1 hierarchy and definition contracts.
4. Define purchasable configurations with dealership package groups.
5. Add DriveSeat overlays using assembly vehicle tuning.

Documentation scope

The website publishes maintained vehicle-development guidance only. The repository's /docs directory also contains architecture plans, QA criteria, migration records, historical case studies, and documentation for unrelated systems. Those records remain available in the repository but are deliberately excluded from this site.

Changes to vehicle identifiers, saved data, asset contracts, or package schemas may require compatibility work. Follow the linked reference documents and ask a programmer before renaming or removing a published identifier.