Work with derived scenes

Inspect scene cards and tables, fix scene metadata at the screenplay source, and avoid disconnected scene records.

Scenes come from scene headings

Laper derives the Scenes dimension from scene_heading nodes in the screenplay. This is why there is no normal “create scene” button in the scene database: creating a detached record would let the project disagree with its own script.

To create a scene, insert a properly formatted scene heading in the screenplay. To rename a location, change the heading. To remove a scene, remove or convert the corresponding scene-heading structure after checking its contents.

Use canvas and table views

The scene canvas is useful for spatial review and visual grouping. The table is useful for scanning structured attributes and comparing many scenes. Both are projections of the same episode data; moving between them does not duplicate anything.

Keep headings stable

Consistent headings help Laper associate repeat locations. Review imported headings that contain unusual dashes, prefixes, or combined location names. If two headings refer to the same set, normalize them in the script. If they represent distinct production spaces, name the distinction intentionally.

Ask AI to work at the source

A request such as “add a scene card” is underspecified. Say where the scene belongs, what it must accomplish, and ask the assistant to insert screenplay nodes in the target episode. It should read the surrounding scene order and use real project identities instead of guessing.

When reordering, treat the screenplay order as authoritative. Verify transitions, setup/payoff, and outline alignment after the move. The scene view should then update from the document rather than requiring a second manual edit.