Skip to content

Production pipeline (Premium) ​

Stages ​

flowchart TD
  A[Script approved] --> B[Shoot - videographer]
  B --> C[Footage clipped and handed off]
  C --> D[Edit - editor]
  D <-->|asset requests| B
  D --> E[Internal review - owner]
  E <-->|revisions| B
  E <-->|revisions| D
  E --> F[Released to client]
  F --> G[Client review - 2 days]
  G --> H[Approved: success]
  G --> I[Changes requested]
  I -->|owner fixes or routes back| E

Vocabulary: VIDEO_STAGES in packages/domain/src/statuses.ts.

Who does what ​

  1. Owner assigns a videographer and an editor to the client (per client, overridable per video). Both then see the client's basic information, scripts and calendar.
  2. Owner writes the scripts and passes them to both. The videographer owns the shooting part (shot list, clips, B-roll); the editor owns the edit.
  3. Shoot day: the videographer films, clips the footage and uploads it to the editor (R2 resumable multipart upload, versioned).
  4. Editor requests: if footage is missing or faulty (stabilisation problem, a replacement clip, missing B-roll), the editor raises a footage request on the video, linked to timestamps or shots. The videographer uploads replacements against that request. Requests have statuses (open, fulfilled, cancelled) and appear on both calendars if dated.
  5. When both parts are done, the video goes to internal review.

Clipping and handoff ​

Clips made in the Clipper app (Clipper guide) can be sent into a video in this app, so the videographer and editor get the footage and the edits without a separate upload. Status: built. Handoff is the one place video leaves the editor's machine (ADR 0012).

  • Who can send: only the videographer or editor assigned to the video, and only to videos they can see (access). Owners and managers do not send clips from the app; they upload from the web app. Sales and clients cannot send.
  • What is sent: the clips chosen in the app, to one video, as its next version. Footage is accepted at the shoot, footage handoff and edit stages; an edit at the edit, internal review and changes requested stages. Each file becomes a video_version row (kind footage or edit), under the same crew upload rules as step 3 above.
  • Which file: the sender picks the file for each send: raw (the unprocessed cut) or processed (the 9:16 video). Footage defaults to raw, an edit to processed.
  • Output modes: built. The Clipper makes processed clips (the default), unprocessed clips (cut at the source's size and frame rate, with handles, no crop, captions or loudness change) or both. Each clip carries up to six markers and an importance (high, medium or low) for the editor. Details in ADR 0014.
  • Frame board: built. Each rendered clip gets ten frames spread across it, stamped with their times on one contact sheet. Each frame is also saved as an image, and frameboard.html in the project folder shows every clip's board. These are files, not database rows.
  • Checks and refusals: a send checks first: each clip must be rendered, or nothing is sent. If one upload fails, the rest are not sent and the message says how many were sent.
  • Audit: the Clipper queues a local handoff.clip event for each clip sent and records the video, kind, version and time on the clip. The server records the crew audit clipper.handoff for each send.
  • Never posts: the app never publishes to a social platform.

Internal review and client review ​

  • Owner review: the owner marks and comments on the video and the script. Each comment is tagged to a role: videographer (footage, shots, B-roll) or editor (cut, captions, colour, audio). Tagged comments go to that person. They fix and resubmit. Repeat until the owner is satisfied.
  • Release: the owner releases the video to the client. A client only ever sees versions the owner released.
  • Client review: the client approves or requests changes, with the same marking and commenting tools, within 2 days (review.clientWindowDays). Their change requests go to the owner first. The owner fixes it himself if he can; otherwise he routes each comment to the videographer or editor by role tag. The fixed version goes back through owner review, then to the client.

DECIDE 6: no client response within 2 days

Default: auto-approve and notify the client. Setting: review.videosAutoApproveOnTimeout.

Marking, highlighting, commenting ​

Must be built in-house; it is the core collaboration tool.

  • Video: comments pinned to a timestamp (or time range), optionally with a drawn region on the frame. Shown as markers on the scrubber.
  • Script: comments on a highlighted text range.
  • Every comment has: author, role tag, status (open / resolved), replies, and which version it was made on. Comments carry forward to the next version as "check this was fixed".
  • Full review history is kept per video.

Comment anchors (timestamp, region, text range) are JSON whose shape will evolve; store them as versioned JSON.

Outcomes and crew records ​

  • Approved → video marked success for both the videographer and the editor; an "Approved" event appears on the calendar.
  • Changes requested by the client → recorded as a disapproval against the person(s) whose role tags were on the client's comments (both if untagged). Internal owner revisions are recorded separately as internal revisions so crew are not penalised twice. These feed crew metrics.
  • The calendar shows: footage hand-off dates, shot-list days, deadlines, successes and progress.

Clipper settings ​

The six clipper.* settings in the registry (packages/domain/src/settings.ts). The owner changes them in Settings; each change is a revision.

SettingDefaultMeaning
clipper.enabledonOff: Clipper apps cannot connect (handshake, AI and sync are refused). Downloads still work.
clipper.ratePerMinute60Requests per minute for each Clipper key. Over the limit the server answers RATE_LIMITED. Provisional.
clipper.monthlyAiRequests600Transcribe, score and metadata calls per user per UTC month. Provisional.
clipper.monthlyAudioMinutes600Audio minutes sent to transcription per user per UTC month. Provisional.
clipper.latestVersionemptyNewest published Clipper version (x.y.z). Empty: none published.
clipper.minVersionemptyVersions below this must update before they connect. Empty: no minimum.

Internal documentation. Not for clients.