Repository navigation
Story dossiers
clippa story new "Jer banned from Kick after the FDA call" --days 7 --dry-run # swarm + triage, the cost
clippa story run jer-banned-kick-fda-call # transcribe, find the moments, write the dossier
clippa story show jer-banned-kick-fda-call # dossier.md again (keeps hand edits)
clippa story add <slug> <video url>... # then: clippa story run <slug> --from triage
clippa story status | trail <slug>
clippa --show kino story plan <slug> # the edit: streams/story-<slug>/story.json (~$0.03)
clippa story cut <slug> # render it, meta, thumbs, the Kitsu cardA brief in, a research dossier out, then a video of it for review. The people
the brief names (by name, nickname, alias or id, from clippa people; --person
adds one) seed the swarm with their YouTube, Kick and Odysee channels. Triage
(Haiku) picks the videos worth transcribing within --max-videos / --max-hours, the people's own
uploads first, and prints the Modal estimate; our own recorded streams are linked, not transcribed
again. Ingest transcribes on Modal (YouTube audio, Kick VOD audio, Odysee) into the archive subject
story-<slug> and indexes it. Find (Haiku) searches that index and any archive subject the swarm
found something in, picks the moments (event, reaction, context) and keeps only quotes that are in
the transcript, in its own wording. The dossier (Sonnet) is a summary, a timeline marked shown /
reported / speculation, people, who said what, conflicts, coverage, gaps and angles, every line
citing moments (M01) or sources (S01); a cite that doesn't resolve is sent back once, then the step
fails. In dossier.json, notes and a source's struck: true survive a rerun. Each step is skipped
when done; --from reruns one and everything after it. Files are in paths.archive/story-<slug>/;
nothing is uploaded until a video of it is approved.
story plan (Sonnet) orders the moments into an edit under a show (--show, [story] show, or
the only one): a title and description, and the moments as parts with a chapter each. Code bounds
each part around its quote ([story] lead_s / tail_s / max_clip_s, at sentence edges), drops a
part that repeats an earlier one's words (a re-upload, our stream playing the video), merges
overlaps and stops at [story] max_minutes; what it left out stays in story.json with
use: false and a note. Edit story.json by hand (use, order, start/end, chapter, the lower
third's channel, title), then story cut renders it: each part from our own source video on the
share or a yt-dlp section of the original, re-encoded with the channel and date on a lower third
and bleeped (the [receipts] renderer), joined into one segment of the stream story-<slug>
(meta.json kind "story", on the show's Kick channel). Meta takes its chapters from the parts and
lists every source with its link in the description ([story] credit); then thumbs and the
Kitsu card, in an episode of its own. A segment retake can't trim a story: edit story.json and
cut again (unchanged parts aren't re-rendered). Approved, it goes out as soon as possible
([story] publish = "asap"), with the hourly uploads.
clippa story cut <slug> --no-review renders the video alone (no meta, thumbs or Kitsu card), for
watching it yourself. It skips sending the story to review; it doesn't block uploads. A story
that was never sent to review has no card to approve, so it never uploads, but re-cutting one that
was already approved replaces the video that approval covers, and the hourly uploads can pick it up.
A viewer who has never heard of anyone in the story shouldn't be dropped into a quote. So the
edit ([story] edit_prompt_version = "v2") is written for them: the parts go in the order things
happened (the dossier's timeline, not the order the videos were posted), and plan writes three
kinds of narration into story.json, using only what the dossier shows ("says" or "reportedly" for
what it marks reported, never a speculation line as fact):
-
tldr: the short version, read first over a title card: who, what happened, each side's account, where it stands. About 20-30 seconds. -
lead_inon each part: one or two sentences before the clip: the date, what you're about to see and who is talking (and that a recap channel is a recap channel). -
close: where it stands and what is still unknown.
story cut makes each one a card (the [receipts] look: a yellow header, the line, the bug)
read by the story's narrator, [story] voice_id (an ElevenLabs voice from clippa narrate voices; not [narrate] voice_id, which is the character's), with [story] tts_settings and
[narrate]'s key, tts_model and format. Each read is cached in streams/story-<slug>/vo/ by its
words and voice, so a re-cut pays only for lines that changed: a story's narration is a few hundred
characters of credits. Without a voice_id the cards are silent and stay up long enough to read
([story] read_wpm). The chapters start at the cards (the short version, each part, where it
stands) and the narration is in the captions. Edit any line in story.json and cut again; the
video is re-cut when a line, the order or the voice changes. [story] narrate = false cuts the
clips alone, and edit_prompt_version = "v1" plans the old clips-only edit. The [bleep] list
applies to the cards: a listed word in a header or title is masked, and a read can't be bleeped, so
cut refuses a narration line with one and names it for you to rewrite in story.json.
A story cut's loudness is [story] lufs (-14, what YouTube plays at); [receipts] lufs stays the
receipts' own. A story cut before this setting existed, or at another loudness, is rendered
again, and its cover picked again, the next time it is cut.
Story dossiers need the swarm's keys plus Modal (as for clippa archive): the videos it picks are transcribed there, on [story] gpu (L4). Kick VODs are
downloaded here at their smallest variant ([archive] kick_format) for their audio; YouTube audio
uses the archive's cookies retry. People and their channels come from clippa people (people.json, with
studio/research_notes/streamers.json, [story] people and the cast library folded in). story cut renders
with [receipts]'s fonts (Impact and Arial Bold, as receipts need) and reads our own streams'
source videos from paths.streams, so it runs on a machine that sees the share; with several
shows, set [story] show or pass clippa --show <key> to story plan.
Home · Getting started · clippa doctor · These pages are built from docs/wiki/ in the repo, so edits made here are overwritten: how to edit them
Run it
- Overview
- Getting started
- Roles and services
- Configuration
- Pipeline
- Review
- Reviewing
- War room
- Clippa messenger
- Scheduling and uploads
- Costs
- Checkup
- Audit
- Backups
Install
- Install
- Install checklist
- Kitsu
- Discord app
- YouTube sign-in
- Windows
- macOS
- Transcribe on Modal
- NAS recorder
- NAS hub
- Claude on the NAS
- Phone access
- Model providers
- Adding a show
- YouTube channel
Features
- Pre-shows
- Fetching VODs
- Speakers
- Faces
- Covers
- Cast library
- B-roll
- Clip art
- Weekly issue
- X posts
- TikTok
- News watcher
- Character pieces
- Documentaries
Research
Working on Clippa