Skip to content
Milk&Ink

Release & Delivery

Approved shots bundle into a Release Package with delivery-spec validation and signed provenance manifests. The handoff format depends on where it's going — Netflix, DCP/IMF theatrical, broadcast, or web.

Release packages

From the project page, Release opens the release vault. Create a package, pick approved ShotVersions, set a target deliveryTarget and deliverySpec. The package validates every included shot against the chosen spec (aspect, resolution, codec, color space, runtime ceiling) and flags mismatches before export.

Delivery spec presets

  • NETFLIX — 4K HDR deliverables, Netflix Originals technical spec.
  • THEATRICAL_DCP — 2K/4K DCP, 24fps, X'Y'Z' color, SMPTE timing.
  • BROADCAST — 1080i / 1080p, BT.709, regional frame rates.
  • WEB — 1080p / 4K H.264, BT.709, platform-agnostic.
  • CUSTOM — override any field per project.

Defaults live in lib/delivery-spec.ts. Overrides stamp onto the package so a late spec change doesn't silently invalidate a previously-validated release.

Provenance manifest

Each ShotVersion in a release carries a signed provenance manifest:

  • Canon fingerprints + versions referenced at render time.
  • Generation packet (prompt, camera, palette, model, seed).
  • Provider used + external job id.
  • Pick decision and approval decision pointers.
  • HMAC signature over the canonical JSON with the workspace signing key.

The format is C2PA-inspired; anyone with the workspace public key can verify a rendered asset's lineage independently. This is the answer to "prove the asset was generated against the canon you claim."

NLE handoff

Export FCP XML v1.11 from any release. The XML includes every shot with frame-accurate rationals (24000/1001 for 23.976, 30000/1001 for 29.97, etc.), so editors can drop the sequence into Final Cut, Resolve, or Premiere and it cuts correctly on first pass.

DCP / IMF

Theatrical targets package additional outputs: DCP XML (composition playlist + asset map), IMF compositions per Netflix / DCP-Bv2.1 profile, deliverable bundles with separate video + audio + subtitle wrappers. Today the bundle is produced as a manifest you hand to a DCP authoring partner; a self-contained DCP encoder is on the roadmap.

Audit trail

Every release event — created, validated, approved, exported, delivered — lands on the hash-chained audit ledger with the package id and HMAC signature. The trail is what a distributor's legal team asks to see; it answers "who approved what, when, and is it tamper-evident?" with one query.

What's next

  • Review & Approval — what approved shots need before they're release-eligible.
  • Canon Bible — the source of the fingerprints the manifest captures.