Sending the shots

In short

• Lorvara pulls shot lists from your brief and creates the prompts you need
• Three steps, in this order: PARSE, SAVE, then SEND (Parse, save, send)
• Send last, always. The shots are read against your brief as confirmed, so they arrive already knowing your cast (Send last)
• The SEND button names whatever is still outstanding, so you are never guessing why it will not go
• Sending commits you to nothing. It lands a draft shot list on one project (What the send does)
• Prompts are written and credits spent only when you confirm it in that project
• A shot list pasted into your brief is set aside, not read into Cast or Props, so your blocks stay clean (It is set aside)
• After a project confirms, edit shots there, but keep adding reference pictures on the brief (After a project confirms)

Most briefs people hand us have the shot list in them. That is fine, and it is handled, but it does not belong in any of the six blocks, so it takes its own path.

It is set aside, not parsed into the blocks

When the document you upload carries a section that reads as a shot list, the parse names it and puts it to one side:

The “Shot list” section (6 shots) is set aside — confirm the blocks, then Continue to Review Scenes & Shots at the end of the brief sends it to a project.

It never reaches Cast, Props or anywhere else. The blocks describe the world; the shots are the work, and the work lives on a project.

The review strip at the top of the page carries it as a sixth row (6 shots under 2 scenes, waiting to be sent to Scenes & Shots), and it counts as a draft remaining, so the strip stays up until the shots have somewhere to go.

Parse, save, send

The Shots block at the foot of the brief has three acts, in order.

40 shots per pass

• The shots in a brief follow the same limit as any shot list: up to 40 per pass
• A longer list is not trimmed. The parse stops and tells you how many shots it counted
• Split it into passes of 40. The project itself has no limit (The shot list)

Parse the shots turns the retained text into rows and scenes, and shows them in the same review table Scenes & Shots uses: the same cards, the same guessed cells, the same edits.

Save the review stores what you have read. Until it is saved, the send will not go: the end-of-brief line says Save the review first.

Continue to Review Scenes & Shots sends it. This is the brief’s one forward act, it sits at the very end of the page, and it is always visible, disabled until it can run, naming exactly what is outstanding:

It says	Because
Intent and Look still to confirm.	A block has no confirmation, or has a newer draft over one.
Save the review first.	The shots are parsed and the review is not saved.
Attach a project first.	The brief is not used by any project.
Every project using this brief has the shots already.	There is nowhere left to send them.

When every block is confirmed and the review is saved, it enables. If more than one project could take the shots, you choose which beside the button.

Send the shots last. They are parsed against the brief as confirmed, so a shot list sent before Cast is confirmed is a shot list that has never heard of your characters.

What the send does, and what it does not

It writes a draft shot list on the project you chose, and takes you to it.

It confirms nothing. The list arrives as a draft for you to review on Scenes & Shots; confirming it there is a separate, deliberate press, and that press is the one that mints prompts and spends.

It composes nothing. No prompt text is written by the send.

It is per project. A brief used by three projects can send its shots to each of them, once each. A project that already has them is refused by name rather than given a second copy.

After a project confirms

Confirming on Scenes & Shots closes that project to the brief’s shot half, and the end-of-brief line changes to say so:

<Project> has confirmed its shots — they are edited on its Scenes & Shots now. Reference images are still added here, on the brief.

Read both halves. The first sends you to the right place to edit a shot. The second is there because people read “not from the brief” as “you are finished here” and stopped adding reference pictures, on the page that is still the only place to add them, and still the only place an entry’s words are edited.

The lock is that project’s. Another project using the same brief is unaffected and can still take the shots.

What to read next

• Drafts and confirming — the six confirmations the send waits on.
• How do Scenes & Shots work? — where the shots land.
• The shot list — why it belongs to the project and not the brief.