cast_otter

Seoul · since 2010Numbers first

@cast_otter

← All works Works · 07

Reel Assembly Line

Test once, render three (9:16 · 4:5 · cover), upload buttons: zero. A person posts one at a time.

In the works

01The problem

A reel is short, but planning, script, assembly, render and upload are scattered. It’s easy to claim “we tried it” without a real test, and auto-upload publishes a mistake in one click.

02How it works · 3 steps

  1. Topic and a real test

    Pick candidates from the teardown playbook and trends; Claude on the Mac runs the tool on fake sample data. Empty tests[] stops the line.

  2. Script, assemble, render

    Claude writes hook, scenes and progress bar; HyperFrames builds the lab-note look, centered, then exports 9:16, 4:5 and cover.

  3. Gate, then approval queue

    Only packs that pass gate_check.sh reel and card enter the approval queue. SuperShy approves one by one. Upload buttons: zero.

03Screens

A reel assembly timeline: vertical preview plus VO, caption and B-roll tracks, with caption text blurred.
Concept screen · DEMO DATA
gate_check.sh reel terminal output: F01–F14 O/X list and an approval-waiting state, with paths blurred.
Concept screen · DEMO DATA
A three-up cover grid for 9:16, 4:5 and cover thumb, with 4:5 crop guides.
Concept screen · DEMO DATA

04Stack

  • Claude · Gemini · HyperFrames · ElevenLabs
  • gate_check.sh reel / card
  • Approval queue (upload_kit)
  • Claude owns test/script/assemble · does not publish

05Status

In the works

Concept. Screens show assembly, gate and covers on fake samples — no account or view counts.