A structure view is only useful if it cannot drift from the draft
Many writing systems begin with a screenplay and then ask the writer to maintain a second database: a scene list, a cast list, a location sheet, and a beat board that may or may not match the latest pages. The duplication looks organized at first and becomes a liability during revision.
Laper takes the opposite approach. The screenplay is the authority. Structural views are projections around it.
When a writer creates or changes a scene heading, Laper can derive the corresponding scene and location information. Character cues contribute to the character layer. The system then presents those entities as outlines, cards, tables, canvases, relationship views, casting views, and storyboard scopes without declaring a separate text document to be the truth.
The derivation chain
The important relationship is simple:
screenplay nodes
├─ scene_heading order → scene order
├─ scene_heading location → location entities
├─ character cues → character entities
└─ scene scope → storyboard and scene-level planning context
The implementation has one load-bearing detail: scenes live in a map, and a map has no narrative order. Laper therefore treats the top-to-bottom order of scene_heading nodes as the only authoritative scene order. The scene metrics scanner walks the screenplay; views that need scene numbers, navigation, or storyboard order use that result.
This matters during revision. Move a scene heading and the structural view can follow the screenplay. A manually numbered spreadsheet cannot.
Derived facts and authored planning are different
Not every piece of story structure should be inferred.
| Data | Relationship to the screenplay |
|---|---|
| Scenes | Derived from scene headings; screenplay order is authoritative |
| Locations | Derived from the location portion of scene headings, then enriched in location views |
| Characters | Derived from character cues, then enriched with profiles, relationships, and casting data |
| Beats | First-class planning entities controlled by the writer or an explicit tool action |
| Props | First-class entities that can be organized and enriched beside the script |
| Storyboard shots | Created within a scene scope by the user or explicit AI assistance |
That separation protects creative meaning. Software can reliably identify a scene heading. It cannot reliably decide that a quiet glance is the thematic midpoint without interpretation. Laper automates deterministic structure and leaves dramatic judgment visible and editable.
Read Scenes, Beats, Props, and Locations for the entity-level workflow and Characters, Casting, and Relationships for the character layer.
One script, several useful lenses
A screenplay page answers “what happens next?” A structure view answers different questions:
- Where does Act Two lose momentum?
- Which scenes use a location that has become too expensive?
- Which character disappears for twenty pages?
- Does a planned beat actually have a scene attached to it?
- Which scene is ready to break into shots?
Laper does not solve those questions by hiding the screenplay. It lets the writer move between page, outline, scene board, character views, beat views, location views, and storyboard while keeping a shared project model underneath.
The AI Script Doctor benefits from the same structure. It can inspect an outline first, locate a structural lesion, and then request the relevant scenes. That is more disciplined than sending a draft to a model with the vague instruction “make this better.”
Structure also improves collaboration
Writers, directors, and producers often read the same project at different resolutions. A writer may live in dialogue; a director may inspect scenes and shots; a producer may look at locations and assets. If those are independent documents, every handoff creates reconciliation work.
Laper synchronizes the project state through Loro, so these views can refer to the same entities. Collaboration does not mean every person must stare at the same screen. It means their screens have a common source.
The technical limits are documented in real-time screenplay collaboration. For the broader product model, return to AI screenwriting software built around the script.
A map that remains accountable to the terrain
Visualization is not decoration. Its value comes from fidelity. By deriving deterministic facts from typed screenplay nodes and keeping authored planning separate, Laper gives the writer a map that can change with the pages without pretending the map wrote the story.