The pipeline.
Every tool reads and writes the same recipe. A design moves from a generator, through search and analysis, into the shared library, and out to a printable mesh — without leaving the suite or converting a file.
From recipe to print.
Solid arrows are the primary flow; dashed lines are recipe imports into mesh. Lab is not shown — it sits alongside the flow as the rigorous stiffness solve, available to any recipe.
One recipe, end to end.
Every design tool emits the same recipe JSON — a description of a scalar field, not a mesh. Design tools never write to the library directly; the recipe is what travels.
sweep ranges a recipe's parameters and homogenizes each sample into a property-tagged batch. ingest is the only writer into the library: batches pass through it for de-duplication and validity classification before they land in vault.
synth runs the inverse direction — it trains on the vault and emits new recipes toward a target, which can re-enter the vault through ingest. lab sits alongside as the rigorous stiffness solve, when an estimate is not enough.
mesh is the exit: it imports a recipe from any source except ingest and produces the watertight 3MF for print.
The rules that hold it together.
Design tools emit a JSON recipe describing a field. They never write to the vault directly.
Sweep homogenizes parameter sweeps over a recipe and outputs property-tagged batches.
Ingest is the only writer into the vault; batches are de-duplicated and validity-classified on the way in.
Synth trains on the vault and emits recipes toward a target; they can re-enter through ingest.
Mesh imports from any source except ingest, and is the only path to a watertight printable mesh.
Every tool in the flow.
Design — wave, tpms, grain, noise, beam, bundle.
Pipeline — sweep, ingest, vault. Inverse — synth. Analyze — lab. Export — mesh.