Skip to content

Spec changelog ​

Newest first. Every change to the spec adds an entry here and bumps SPEC_VERSION in packages/domain/src/spec.ts (rules).

1.4.0 ​

Owner asked for clips the editor can cut from at source size, with markers and an importance to choose between them.

  • ADR 0014: the Clipper makes processed clips (9:16, the default), unprocessed clips (source size and frame rate, handles, no overlays) or both. Each clip has up to six markers and an importance (high, medium or low). Review proxies are scan copies that are never sent.
  • Production: handoff picks the file for each send. Footage defaults to the unprocessed cut, an edit to the processed video.
  • Glossary: Processed clip, Unprocessed clip, Handle, Marker, Importance, Review proxy.
  • Impact on existing data: none. No tables change. markers, importance and raw are optional fields in the local project file.

1.3.0 ​

Owner asked for the Clipper to pick moments by what is on screen, not only by sound and words, as tools like Opus Clip do.

  • ADR 0013: online, the Clipper cuts up to four small still frames for each of the top 24 candidates and sends them with the score request, when the server's model accepts images. Video never leaves the machine. The model returns a one-sentence visual summary and up to four on-screen moments per candidate, which feed the title and the marker labels. Without images the Clipper scores from text only.
  • Stack: Clipper AI calls may carry still frames, never video.
  • Glossary: Keyframe.
  • Impact on existing data: none. No tables change; stills are billed as image tokens in the Clipper usage meter.

1.2.0 ​

Owner asked for the Clipper to be specified, with a frame board for each clip and a way to send clips into the app's production flow. Also refreshes stale status text.

  • Production: clips are sent to a video as its next version through /clipper/v1/videos: footage by the assigned videographer, edits by the assigned editor. Owners and managers are excluded. The frame board gives each clip ten frames on a contact sheet, with each frame and a frameboard.html page.
  • Production: the six clipper.* settings.
  • Access: who may create Clipper keys (owner, manager, editor, videographer) and who may send clips (assigned videographer or editor only). Owners and managers hold keys and see usage and the library; they upload from the web app.
  • Data model: Clipper tables (built); status column refreshed for Business, Sales, Leads, Commercial, Calendar, Content, Client tools and Crew, which were marked Planned though their migrations exist.
  • Stack: Clipper row and the AI-calls constraint.
  • Glossary: Clipper terms.
  • Open decisions: decision 13 resolved: owners and managers do not send clips from the app. Three provisional Clipper limits.
  • ADR 0012: handoff, the one exception to "video never leaves the machine".
  • Fix: the index still showed spec version 1.0.0.
  • Impact on existing data: none. New apikey and clipper_* tables (migration clipper_server). Handoff adds video_version rows; the clip's handoff record is saved in the project file on the user's machine. Frame boards are files in the project folder, not tables.

1.1.0 ​

Owner supplied the research approach (Reroot's client scrape) and asked for it to run for clients as well as leads.

  • Leads and research: the scraper guideline is answered. Research runs for leads and clients, reads websites with Cloudflare Browser Rendering, finds social accounts, videos, process and market information, and uses Claude (the Claude app in development, the Claude Platform in production).
  • Open decisions: decision 11 (scraper guideline) answered.
  • Impact on existing data: none (new tables; no earlier research data existed).

1.0.0 ​

Imported the owner's "shoot&grow-crew: the whole system, explained for a developer" as the baseline, split into chapters.

Clarifications made during import (no behaviour change):

  • Event scope gained own_user for payday and personal unavailability rows, which the original scope list could not express (Global calendar).
  • Chapter ids were assigned so the app can link to them; section numbers from the original were dropped.
  • Every DECIDE item became a numbered row in Open decisions and, where it is a switch, a setting.
  • Three values the spec left as "N" were given provisional defaults (listed in Open decisions), plus one for booking hours and one for signed-link lifetime.

Additions that are engineering notes, not owner decisions, and are labelled as such where they appear:

  • Content schedule: generated events are stored when generated; a settings change does not silently rewrite them.
  • Data model: ids, timestamps, money and status conventions.

Open items carried over: decisions 1–12.

Internal documentation. Not for clients.