Eve library

ISIS v2 FBX Output Schema and Metadata Contract

Guide

Revision 1

On this page

Generated: 2026-03-06T09:17:23.235Z Checklist: MXD-0041 (ISIS2-01231) Format: fbx (model/vnd.autodesk.fbx) Phase: Phase 4 | Milestone: M3 Launch (2026-07-27 to 2026-10-30)

Objective#

Define a canonical schema and metadata contract for FBX outputs with rig and animation safeguards, deterministic integrity metadata, and workflow provenance suitable for DCC interchange and game-ready skeletal handoff.

Canonical Schema#

  • Schema ID: isis.v2.output.fbx.package
  • Schema Version: 1.0.0
  • Binary signature: 4B 61 79 64 61 72 61 20 46 42 58 20 42 69 6E 61 72 79
  • Required top-level fields:
    • schemaVersion
    • format
    • fbxVersion
    • binary
    • nodeCount
    • meshCount
    • materialCount
    • polygonCount
    • upAxis
    • embeddedMedia
    • animationStackCount
    • skeletonCount
    • hasBlendShapes
    • 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
mesh-package WARM mesh/main.{obj,fbx,gltf,glb}, mesh/topology-report.json

Supported Output Classes#

Output Class Package Classes
mesh_package mesh-package

Applicable Asset Families#

Asset Family Output Classes Naming Rules

Validation Invariants#

  • Animation-cache FBX outputs require at least one animation stack.
  • Rig-source FBX outputs require at least one skeleton.
  • FBX outputs with blend shapes require at least one mesh.
  • Embedded media requires binary FBX packaging.
  • RegisterOutputRequest mimeType must be model/vnd.autodesk.fbx, type must be 3d-model, and storage.key must end with .fbx when fbxPackage is supplied.
  • FBX 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-fbx-output-schema-metadata-contract.mjs

Acceptance Criteria#

  • Output registry accepts first-class FBX package metadata with strict validation over rig and animation metadata, embedded media rules, artifact-role constraints, and manifest checksum fields.
  • Canonical FBX contract enumerates the package classes and output classes that legitimately emit FBX artifacts under the shared output taxonomy.
  • FBX manifest provenance preserves workflow-variant and dependency-manifest linkage needed for deterministic downstream ingest of rig and animation interchange artifacts.
  • Validator and schema tests catch invalid FBX registrations and enforce the canonical metadata surface.

Traceability#

  • Checklist item: MXD-0041
  • Ticket key: ISIS2-01231
  • 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