Eve library

ISIS v2 USD Output Schema and Metadata Contract

Guide

Revision 1

On this page

Generated: 2026-03-06T09:37:42.615Z Checklist: MXD-0053 (ISIS2-01243) Format: usd (model/vnd.usd) Phase: Phase 4 | Milestone: M3 Launch (2026-07-27 to 2026-10-30)

Objective#

Define a canonical schema and metadata contract for USD outputs with composition-arc coverage, layer-encoding signaling, deterministic manifest metadata, and workflow provenance suitable for scene, layout, rig, and shot-cache interchange.

Canonical Schema#

  • Schema ID: isis.v2.output.usd.package
  • Schema Version: 1.0.0
  • Binary signature: 23 75 73 64 61 / 50 58 52 2D 55 53 44 43
  • Required top-level fields:
    • schemaVersion
    • format
    • underlyingEncoding
    • defaultPrim
    • primCount
    • meshPrimCount
    • skeletonCount
    • subLayerCount
    • referenceCount
    • payloadCount
    • variantSetCount
    • timeSampledAttributeCount
    • upAxis
    • artifactRole
    • manifest
  • Manifest fields:
    • filename
    • mimeType
    • checksumAlgorithm
    • checksum
    • generatedAt
    • provenance
  • Provenance fields:
    • assetFamilyId
    • workflowId
    • workflowVariant
    • promptFingerprint
    • seed
    • modelId
    • dependencyManifestRef

Supported Package Classes#

Package Class Storage Tier Required Artifacts

Supported Output Classes#

Output Class Package Classes

Applicable Asset Families#

Asset Family Output Classes Naming Rules

Validation Invariants#

  • USD frame ranges require both frameRangeStart and frameRangeEnd when either endpoint is present.
  • frameRangeEnd must be greater than or equal to frameRangeStart.
  • Shot-cache USD outputs require time-sampled attributes.
  • Rig-source USD outputs require at least one skeleton.
  • defaultPrim must be a valid USD prim identifier.
  • RegisterOutputRequest mimeType must be model/vnd.usd, type must be 3d-model, and storage.key must end with .usd when usdPackage is supplied.
  • USD manifest checksum uses sha256 and must preserve workflow/dependency provenance linkage.

Verification Commands#

  • pnpm --filter @isis/output-registry exec vitest run src/schemas/output.schema.spec.ts
  • node scripts/isis/validate-v2-usd-output-schema-metadata-contract.mjs

Acceptance Criteria#

  • Output registry accepts first-class USD package metadata with strict validation over default prim identity, composition-arc counts, frame ranges, rig and shot-cache signaling, and manifest checksum fields.
  • Canonical USD contract enumerates the currently supported package classes and output classes that legitimately emit USD artifacts under the shared output taxonomy.
  • USD manifest provenance preserves workflow-variant and dependency-manifest linkage needed for deterministic downstream ingest of layered scene interchange artifacts.
  • Validator and schema tests catch invalid USD registrations and enforce the canonical metadata surface.

Traceability#

  • Checklist item: MXD-0053
  • Ticket key: ISIS2-01243
  • Source references:
    • docs/domains/isis/remediation-v2/ISIS_REMEDIATION_V2_TICKETS.json
    • docs/domains/isis/remediation-v2/ISIS_V2_OUTPUT_PACKAGE_TAXONOMY.json
    • apps/isis/output-registry/src/schemas/output.schema.ts
    • apps/isis/output-registry/src/schemas/output.schema.spec.ts
    • apps/isis/output-registry/src/services/output.service.ts
    • apps/isis/output-registry/src/types.ts
    • ISIS_TODOS_2.md