Eve library

ISIS v2 ABC Output Schema and Metadata Contract

Guide

Revision 1

On this page

Generated: 2026-03-06T09:43:39.548Z Checklist: MXD-0057 (ISIS2-01247) Format: abc (application/alembic) Phase: Phase 4 | Milestone: M3 Launch (2026-07-27 to 2026-10-30)

Objective#

Define a canonical schema and metadata contract for Alembic outputs with cache-role validation, storage-backend signaling, deterministic manifest metadata, and workflow provenance suitable for baked geometry, animation, simulation, and camera handoff.

Canonical Schema#

  • Schema ID: isis.v2.output.abc.package
  • Schema Version: 1.0.0
  • Binary signature: 89 48 44 46 / 4F 67 61 77 61
  • Required top-level fields:
    • schemaVersion
    • format
    • storageBackend
    • topObjectName
    • objectCount
    • xformCount
    • polyMeshCount
    • curvesCount
    • pointsCount
    • cameraCount
    • materialBindingCount
    • timeSamplingCount
    • sampledFrameCount
    • hasFaceSets
    • hasVisibilitySamples
    • 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#

  • Alembic frame ranges require both frameRangeStart and frameRangeEnd when either endpoint is present.
  • frameRangeEnd must be greater than or equal to frameRangeStart.
  • Animated Alembic caches require at least two sampled frames.
  • Camera-cache Alembic outputs require at least one camera.
  • Geometry-cache Alembic outputs require geometry primitives.
  • Alembic outputs with face sets require at least one poly mesh.
  • RegisterOutputRequest mimeType must be application/alembic, type must be 3d-model, and storage.key must end with .abc when abcPackage is supplied.
  • Alembic 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-abc-output-schema-metadata-contract.mjs

Acceptance Criteria#

  • Output registry accepts first-class Alembic package metadata with strict validation over cache role, storage backend, frame sampling, geometry and camera coverage, and manifest checksum fields.
  • Canonical Alembic contract enumerates the currently supported package classes and output classes that legitimately emit Alembic artifacts under the shared output taxonomy.
  • Alembic manifest provenance preserves workflow-variant and dependency-manifest linkage needed for deterministic downstream ingest of baked cache interchange artifacts.
  • Validator and schema tests catch invalid Alembic registrations and enforce the canonical metadata surface.

Traceability#

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