Blender AI Production System

Overview

Blender work is treated as a build, not as a hand-edited file. A scene is produced by running code, so it can be rebuilt, reviewed and versioned like any other software output.

Why it exists

Hand-made 3D files are hard to review, hard to reproduce and easy to lose track of. Building scenes from code keeps the source readable, makes every change visible in version control and lets agents take part in the work through the same scripts a person would run.

Current capabilities

• Headless builds. Blender runs in background mode and executes a Python build script. Build time depends on model complexity.
• Stable object identity. Every generated object has a stable part ID, so renders, exports and the website refer to the same thing.
• Evidence per object. Each object records how well it is known (measured, photo, catalogue, published, generic).
• Review tooling. Quick-look renders, object-ID renders laid over calibrated photographs, and overlap and clearance checks.
• Web export. One build produces a GLB model and a part registry for an interactive viewer.

Architecture

instruction
   ↓
agent or person
   ↓
Blender build script (Python, background mode)
   ↓
scene with stable IDs and evidence levels
   ↓
validation (overlap, clearance, photo match)
   ↓
render / GLB export + part registry

3D interface

The pipeline's first public output is the CHS 275 twin. Its export is a checksummed release, and every object in it can be browsed on spacecorp.io:

• Viewer. The Audi A8 D2 project page opens the published model in an interactive viewer when asked. Selecting an object shows its part ID and evidence level.
• Part objects. Every exported object has its own part page and API record (/v1/parts), grouped by the system the build assigned it to.
• One identity. The part ID in the Blender scene, the GLB node, the web page and the API is the same.

Audi digital twin production

The Audi A8 D2 twin is the car currently built with this method. The car, its evidence and its published model belong to CHS 275. This project keeps the reusable method: code-driven Blender builds, stable component identities, evidence levels, validation, rendering and GLB export. Audi consumes that method by running its own build and publishing a checksummed model. The tooling is not copied into a second implementation, and it is not packaged as a separate release.

• Model. The Audi project and its systems and parts.
• Evidence. Evidence levels in a code-built digital twin.
• Releases. CHS 275 twin 0.3.0, 0.2.0 and 0.1.0. A published model is never replaced.

Not yet published

No packaged release of the pipeline exists yet. Source .blend files and build scripts are not published on spacecorp.io. The current model export is the CHS 275 twin 0.3.0; the previous immutable 0.2.0 and 0.1.0 exports remain available.