❯ techcly stages --verbose

One process, eight stages

Nothing is handed off, because there is nobody to hand it to. Eight stages execute in order inside one job, each writing something you can read, and each one yours to overrule before the next is scheduled.

01briefin: one line of text→out: angle, audience, target length

The sentence is parsed as a request, not a prompt. It emits a brief you can read and argue with before a single word of script exists.

02scriptin: brief→out: timed narration

Written against the duration target rather than cut back to it afterwards, so pacing is a design decision instead of a rescue.

03storyboardin: script→out: scenes[]

Emits an array of scenes. Each one holds a line to read, a picture to hold it over, and the seconds it is allowed to take.

04visualsin: scenes[]→out: frame per scene

Each frame is generated from that scene’s own description at the project’s aspect ratio — 16:9, 9:16, 1:1 or 4:5.

05voicein: scenes[]→out: audio per scene

One voice per project, one of six languages, read so it fits inside the seconds the scene was allocated.

06captionsin: audio→out: timed cues

Cues are measured against the rendered audio rather than guessed from the script, and remain editable to a tenth of a second.

07renderin: everything above→out: mp4

FFmpeg composites picture, motion, audio and cues into one file, emitting a percentage and a thumbnail while it works.

08exportin: mp4→out: signed url

A signed URL you can hand to anyone. The file belongs to you, commercial use included.

How the job behaves

Re-run one stage: Any single scene can be regenerated in place. Nothing else in the job moves, which is what makes this an edit rather than a re-roll.
Two halt points: The pipeline halts once the storyboard exists and once more before the render is submitted. Both halts wait for you indefinitely.
Reserved, then settled: Credits are reserved when a stage starts and settled when it emits. A failed stage releases its reservation on the spot; there is nothing to claim.
Templates and brand kits: Presets for the jobs that come round often. Logo, palette and type are pinned to the project, so the export reads them instead of asking you.
Teams: One workspace per team, joined by email invitation. Membership is the only permission model, and there is nothing to buy per editor.
Safeguards: Prompts pass moderation, exports sit behind expiring signed URLs, and full card numbers and security codes are never written to our servers.

❯ techcly run "your idea here"

Ship your first one