# Comments, dialogue actions, transitions, narration > Four helper types, each answering a different question—and what per-line intent is for. Source: https://loomworld.ai/docs/editor-annotate ## What the four supporting types separate Dialogue action, transition, narration and comment are not dialogue. Each answers a different question—what happens on stage, how scenes cut, who is narrating, and which words are only for you. Once they are separated, the editor can style them apart, AI can tell a line from a stage business, and rereading does not depend on indentation. ## Dialogue action: alongside the line, or in a description Dialogue action (key 5) is what happens while a line is being said: he rises as he speaks, pushes the letter across the table. It hangs inside the dialogue structure and cannot create a speaker—there has to be a character line above it. A passage with movement and no dialogue at all belongs in a description line: that is narration of the scene, not an insertion into somebody’s sentence. ## Transition: write the cut down Transition (key 7) marks the seam between scenes—fade in, blackout, jump cut, three years passing. It is a structural note, not decoration: placed between two scenes it tells reader and AI alike that the previous unit ended here. ## Narration: the narrator’s voice Narration (key 6) is the narrator or an offscreen voice, kept apart from character lines. It is the only narrative node in the product: the legacy caption type is gone and is not silently re-read as narration, so you never maintain two near-identical kinds. ## Comment: only for you Comment (key 4) is a memo to yourself—“explain this motive later”, “rewrite once the rule entry exists”. It ends the current speaker, which matters more than “it is just a sticky note”: never park a line of dialogue in a comment. Comments are part of the script and travel with saves and exports. Whether to keep them in a delivery is your call. ## Per-line intent: one sentence for the AI Beyond the type, each line can carry a short note about what this line is for. It is not reader-facing text; it tells whoever continues the work what the line must do. Continuation, beat expansion and consistency checks all read it, so one sentence now saves a paragraph of explanation later. Chapters, scenes and scene settings each have their own note too (chapter intent, scene summary, scene setting description). They do not replace the per-line one. The three layers shown together, and the “to write / to tidy” states, are in [Chapter companion](https://loomworld.ai/docs/chapter-companion). ## Four questions that pick the type for you - Movement but no line spoken? Use Description. A dialogue action is an insertion inside somebody’s sentence; with no speaker there is nothing to insert into. - A seam between scenes, or a shift inside one scene? The seam is a Transition; the shift inside is a Scene setting. - Whose voice is this? A character’s words need a character line above them claiming the speaker; a narrator or an offscreen voice is Narration. - Who is it for? A memo to yourself is a Comment; a note to collaborators and to the AI about what this line must do is the per-line intent field. Get the distinction right once and the rest follows automatically: rendering by type, appearance counts by type, the AI telling a line from stage business, and each kind landing in its own place on export. ## Limits and troubleshooting - Supporting types are never detected or filled in for you: Loomworld does not guess which sentence is an action, nor insert transitions. - A line of dialogue with no speaker: check that a character line sits above it—dialogue always belongs to someone explicit. - Type changes meaning, not text. Pick wrong, Tab again, choose Description.