Inside every beat is a Beat Sheet. Prose — write the beat in plain language. @Nina reaches the wooden bench and sits. The movement is heavy, as if the act of walking was an immense chore. TypeDocumentation Index
Fetch the complete documentation index at: https://docs.loraverse.io/llms.txt
Use this file to discover all available pages before exploring further.
@ to reference any entity from your library. The mention becomes a structured token that travels into every shot under this beat.
Dialogue blocks — character-tagged lines that get treated as dialogue, not narration. Nina: “You’re my only friend.” These render distinctly from prose and feed downstream into shot-level dialogue.
In the Inspector, the same beat shows up as a structured summary. The prose distilled into the parts a director would actually use on set.
Story Function — what this beat is for. Reveal, setup, confrontation, turn, climax. It tells Loraverse, and you, what role this beat plays in the larger arc.
Pacing — how this beat moves. Measured, urgent, languid. Tone for rhythm, not just speed.
State Change — what’s different by the end of the beat that wasn’t true at the start. A character realized something. A relationship shifted. The mood broke. State change is screenwriting’s core question: what changes? If a beat doesn’t change anything, it’s probably not a beat.
These aren’t arbitrary fields. They’re the questions a screenwriter or director would ask of every beat in a script. Loraverse just holds the answers in a place the system can read. The Beat Sheet is where the writing lives. The shots beneath it are where the writing gets shot.