6. Production Resources

One context-bearing artifact model

Storyboards, scripts, wardrobe looks, lighting references, VFX versions and operational documents differ in content. They nevertheless share useful needs: ownership, context, versions, visibility and review. A Production Resource supplies those common relationships without pretending every media type has the same capture or preview behavior.

A resource can connect to a person, assignment, scene, shot, group or Production Day. These links explain what the artifact concerns. They do not automatically give a linked person permission to retrieve or approve it.

Exact content identity

A Resource Version is an immutable snapshot. A review identifies that version, not a moving “latest” attachment. Uploading another version cannot transfer old approval onto new content.

Current version, latest approved version and final version answer different questions. The current version may be awaiting review while an earlier version remains approved or final. Finalization is an explicit operation concerning the appropriate approved content; it is not merely another spelling of upload success.

interface ResourceExample {
  productionId: string;
  context: {
    personIds: string[];
    assignmentIds: string[];
    sceneIds: string[];
    shotIds: string[];
    productionDayIds: string[];
  };
  currentVersionId?: string;
  approvedVersionId?: string;
  finalVersionId?: string;
}

This representative contract is independently authored and deliberately simplified.

Common infrastructure, specialized adapters

Media admission, private delivery and native capture retain their own boundaries. A common Resource model does not imply a generic public download URL or a complete streaming platform. Shared review mechanics do not eliminate type-specific validation.

The documented Resources implementation is local. Focused automated evidence exists, while production release, physical-device capture and staged department acceptance remain pending. This distinction is part of the architecture story: source and local checks are necessary evidence, but they are not substitutes for the relevant operational acceptance.