Pipeline

Five deterministic stages between your repository and a 3D build.

01

Interception

The agent runs as a cloud-side proxy over your Git remotes, package registries and artifact buckets. Nothing is mirrored blindly — each event is normalised into a typed record before it enters the graph.

  • Commit stream
  • Dependency manifest
  • Asset ledger
02

Consolidation

Duplicate modules, forked utilities and orphaned assets collapse into a single canonical graph. Conflicts are surfaced as reviewable diffs instead of silent overwrites.

  • Canonical graph
  • Conflict report
  • Ownership map
03

Fragmentation

The graph is cut along dependency seams into fragments sized for parallel compilation and streaming delivery. Cuts are deterministic, so two runs on the same input produce identical fragments.

  • Fragment set
  • Build order
  • Cache keys
04

Tagging

Every fragment carries beacons: domain, level of detail, target platform, licence and lifecycle state. Downstream builds read the beacons rather than bespoke configuration.

  • Beacon index
  • LOD ladder
  • Licence trail
05

Spatial build

Tagged fragments compile into scene graphs, meshes and metadata, then ship to your engine target or straight to a WebGL viewer for review.

  • Scene graph
  • Engine package
  • Review link