01
Start from the product
Use exact product revisions, source URLs, dimensions, images, GLB, or STEP as modeling evidence.
Solution · 3D product workflows
Move from product evidence to a reviewed 3D revision.
The 3D workflow is designed around product identity and checkpoints: source evidence enters the project, agents and deterministic modeling tools create revisions, and a human decides what artifact becomes part of the product.
02
Route the work
Use build123d for deterministic CAD and Blender for mesh, scene, render, or repair operations.
03
Approve the artifact
Checkpoints and review separate generated output from an approved product model.
Project contract
The running job should never silently change underneath the agent.
A Studio job snapshots its manifest, source set, product revision, runtime/model profile, and requested operation. New user changes become the next revision instead of mutating the active run.
Manifest snapshot
Exact source/product revision and requested pipeline are fixed for the running job.
Object ticket
The runner receives the exact object/project operation instead of guessing which scene element to modify.
Checkpoint artifact
Intermediate and final artifacts remain reopenable for comparison and revision requests.
Cleanup lifecycle
Temporary worker data is separated from durable project state and reviewed artifacts.
Modeling stack
Agent intent on top. Specialized workers underneath.
ConfigAI can evolve the worker layer independently from the product workspace as better CAD, Blender, reconstruction, segmentation, and material tools become available.
Modeling agent
Plans the change from product semantics, evidence, prior checkpoints, and user instruction.
build123d worker
Parametric and deterministic CAD operations where exact geometry is more important than generative approximation.
Blender worker
Mesh editing, scene operations, conversion, validation, material/UV work, and rendering.
Specialized 3D workers
Image-to-3D, semantic part labeling, material generation, and later USD tooling plug into the same project/review contract.
Expandable
Product attach
A reviewed artifact becomes a product revision deliberately.
Approval can attach a model to an existing product revision or create a new draft product when the modeling project began before a structured product existed.
01Review checkpointInspect the artifact, source evidence, model history, verified facts, and assumptions.
02Approve or request revisionKeep the artifact in project history even when it is rejected or needs another iteration.Human gate
03Attach to productBind the approved artifact to the exact product revision with optimistic concurrency checks.
04Reopen laterStart a new Studio revision from the product and retain the approved model as the previous checkpoint.
ConfigAI
Treat 3D as product history, not an attachment folder.
The modeling stack can change over time while the source, revision, checkpoint, and review contract stays stable.