Eve library
ISIS v2 MOV Output Schema and Metadata Contract
Guide
Revision 1
On this page
Generated: 2026-03-06T08:49:37.936Z Checklist: MXD-0025 (ISIS2-01215) Format:
mov (video/quicktime) Phase: Phase 4 | Milestone: M3 Launch (2026-07-27 to
2026-10-30)
Objective#
Define a canonical schema and metadata contract for QuickTime MOV outputs with
atom-level validation, editorial timecode safeguards, alpha-capable mezzanine
codec coverage, deterministic integrity metadata, and workflow provenance
suitable for ProRes masters and review cuts.
Canonical Schema#
Schema ID: isis.v2.output.mov.package
Schema Version: 1.0.0
Binary signature: 66 74 79 70 71 74
Required top-level fields:
schemaVersion
format
width
height
durationSeconds
frameCount
frameRate
videoCodec
videoProfile
pixelFormat
colorSpace
artifactRole
majorBrand
compatibleBrands
atomInventory
moovPlacement
containsAlpha
timecodeTrack
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
video-master
HOT
masters/video-master.{mp4,mov,mxf}
Supported Output Classes#
Output Class
Package Classes
video_master
video-master
Applicable Asset Families#
Asset Family
Output Classes
Naming Rules
cinematic-shot-sequence
video_master
FN-001
Validation Invariants#
ftyp, moov, mdat, mvhd, trak, mdia, hdlr, minf, stbl, stsd, stts, stsc, stsz,
and stco atoms are mandatory for every MOV output.
MOV atomInventory values must be unique.
compatibleBrands must include the declared majorBrand.
ProRes MOV outputs require a ProRes-compatible videoProfile, while DNxHD MOV
outputs require a DNxHR profile.
h264 MOV outputs require videoProfile high, h265 MOV outputs require
videoProfile main10, and animation MOV outputs require videoProfile 4444.
Alpha-bearing MOV outputs require prores or animation videoCodec and
yuva444p10le or rgba pixelFormat.
Editorial MOV outputs require a timecode track, and timecodeTrack requires
tmcd atom coverage.
RegisterOutputRequest dimensions, duration, and frameCount must match
movPackage metadata when supplied.
RegisterOutputRequest mimeType must be video/quicktime and storage.key must
end with .mov when movPackage is supplied.
MOV 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-mov-output-schema-metadata-contract.mjs
Acceptance Criteria#
Output registry accepts first-class MOV package metadata with strict
validation over QuickTime atom inventory, codec/profile compatibility,
alpha-bearing mezzanine encodes, editorial timecode signaling, and manifest
checksum fields.
Canonical MOV contract enumerates the package classes and output classes that
legitimately emit MOV artifacts under the shared output taxonomy.
MOV manifest provenance preserves workflow-variant and dependency-manifest
linkage needed for deterministic downstream ingest of editorial masters and
review renders.
Validator and schema tests catch invalid MOV registrations and enforce the
canonical metadata surface.
Traceability#
Checklist item: MXD-0025
Ticket key: ISIS2-01215
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
docs/domains/isis/remediation-v2/ISIS_V2_CINEMATIC_SHOT_SEQUENCE_OUTPUT_PACKAGE_CONTRACT.json
ISIS_TODOS_2.md