Eve library

ISIS V2 3D Output Package Contract

Guide

Revision 1

On this page

WS06-001 introduces a first-class, typed three_d_package/threeDPackage contract across:

  • workflow schema (output_spec.three_d_package)
  • generation API job output payloads (output.threeDPackage)
  • output registry registration/update contracts (threeDPackage)
  • SDK/client response types

Required Components#

Component Required Purpose
mesh yes Canonical mesh delivery object (glb/gltf/fbx/obj/usd/usda/usdc/usdz/stl/ply)
materials yes Material manifest contract with workflow semantics
textures yes Slot-indexed PBR texture set contract
metadata yes Package manifest and provenance envelope
preview_turntable / previewTurntable yes Review-ready turntable render contract

Workflow Contract (output_spec.three_d_package)#

3D workflows (output_spec.type: "3d_model" or primary.type: "3d_model") are now required to define:

  • mesh artifact id/path/format (+ optional LOD and geometry budget metadata)
  • materials artifact id/path/format + material workflow
  • textures artifact id/path/format + required and optional slots
  • metadata artifact id/path/format + manifest version
  • preview turntable artifact id/path/format + timing metadata

Linting now derives/validates required bundle artifacts from the 3D package contract.

API/Registry Contract (threeDPackage)#

3D outputs now expose a typed package object containing:

  • mesh identity + format + topology summary
  • material descriptors and texture references
  • texture file slots and color-space metadata
  • package metadata manifest
  • preview turntable media descriptor

This structure is accepted by generation and output-registry contracts and persisted via output metadata.