CHS 275

Overview

The project covers one car, a 1996 Audi A8 D2 4.2 quattro known as CHS 275. It keeps the car's evidence, its written record, a 3D twin and the tools used to work on it in one place, so that every statement about the car can be traced back to a photograph, a document or a measurement.

Why it exists

Information about an older car tends to scatter across receipts, manuals, photographs, forum threads and memory. The project treats the car as a technical object with a hierarchy (vehicle, system, assembly, component, part) and keeps one authoritative record instead of several partial ones.

Current capabilities

• One record. A single written account holds the car's facts. Other outputs, such as an offline dossier and a garage sheet, are generated from it and never edited by hand.
• A twin built from code. The whole car is built in Blender from Python: body, space frame, closures, glass, interior, engine, gearbox, driveline, axles, brakes, wheels, exhaust, fuel, cooling and the fasteners that hold them together. Every part and every bolt is its own object with a stable part ID.
• Labelled uncertainty. Every part carries an evidence level: measured, photo, catalogue, published or generic. Uncertain parts are shown and labelled rather than left out.
• A website. AppAudi presents the car's story, specification, maintenance notes and the twin in an interactive 3D view. A privacy scan stops private material from reaching its public build.
• Diagnostics. A command-line tool reads fault codes and live data over the K-line with a KKL cable and can practise against a simulated car.

Architecture

evidence (photos, papers, lookups)
        │
        ▼
single written record ──► generated dossier and garage sheet
        │
        └──► status data (private)

Blender build from Python ──► GLB model + part registry ──► website 3D view

How the twin is produced

The car-specific model belongs to this project. The reusable Blender method — code-driven builds, stable component identities, evidence levels, validation, rendering and GLB export — belongs to the Blender AI Production System. This project runs that method and publishes the checksummed GLB. It does not keep a second copy of the tooling, and the tooling is not a separate package.

The evidence rules are written up in Evidence levels in a code-built digital twin. The published models are 0.3.0, 0.2.0 and 0.1.0. The studio at spaceframe.spacecorp.io loads 0.3.0.

Published here

• The 3D twin, version 0.3.0. The GLB model is a versioned release with a SHA-256 checksum and the source commit it was built from. It contains 2,241 stable part objects. This is the file the studio loads: clearer glass, a softer clearcoat, headlamp bowls visible through the lenses, tyre lettering on the upper sidewall, and separate steering outer ends. The night garage is unchanged. Geometry remains photo-informed or generic where labelled, not factory CAD. A published file is never replaced; 0.2.0 and 0.1.0 remain available.
• Specifications as facts. The values in the specification tables are individual facts. Each fact names its source and page and states how it was obtained. Values copied from a document by an AI agent stay marked unverified until a person has checked them against the source.
• Factory reference versus this car. ABZ engine data comes from Audi's factory training material and describes the engine type, not a measurement of this car.

Not published

The dossier and the evidence archive are not published on spacecorp.io. The VIN, registration documents, service costs and per-part status are private and stay private. The part registry that accompanies the model is withheld for the same reason.