PLANNING

The shot list is the project

A board is an ordered list of shots, each citing a scene, a cast, a location and the project look. It is the only place the plan lives.

BRIEF → BOARD → PREVIZ

01DraftA brief becomes scenes and beats.
02Break downBeats become shots with cast and duration pre-filled.
03PrevizRender each shot as a cheap still for approval.
04ApproveA human signs off, then the board is shootable.
Previz is the cost gate. Approve stills before anyone spends money on video.

Calls

story.draft(brief)
Brief in, structured scenes and beats out.
story.to_board(story)
Break the story into shots with entities resolved.
board.previz(project)
Render every shot as a still. Cheap, fast, reviewable.
board.reorder(ids)
Change shot order. Continuity references re-resolve.
RequestPOST /v1/board/previz
{
  "project": "prj_4a81b",
  "shots": "all"
}
Response200 OK
{
  "job": "job_2be07",
  "shots": 14,
  "est_cost_usd": 0.42
}
From the CLI
$ picx story draft --brief brief.md
$ picx board build
  ✓ 14 shots · est. 31s
$ picx board previz
  ✓ 14 stills → ./previz/

For users

Previz first, always. Stills cost cents and video costs dollars — catch a wrong plan while it is still cheap.

For developers

board.previz returns an estimated cost before it runs. Surface that number in your UI and gate the shoot behind an explicit confirmation.

Gotchas

  • Reordering shots re-resolves continuity frames, which can invalidate takes. The API tells you which ones.
  • A shot with an unlocked character will not previz — lock the cast first.