Organizing Context
Start with the Story you are writing. Keep its lasting background in Story Context, structure-specific development in Storyform Context, and conversation-specific files in Files. Your Working Context selects the Story, Storyform, and Persona for your work; Ideas provides a personal place for thoughts that need no assignment.
An Individual Project can remember that selection while you work alone. You can organize more Stories and Storyforms or invite collaborators later. Read What You Work On for the starting workflow and Collaboration and Projects when you need broader organization or sharing.
Check your working material
Open the work you want to develop. In Automatic, Working Context follows its Story and Storyform, so ordinary writing needs no separate source setup. Choose Custom references when the task calls for different material: the series bible can inform an episode while new development belongs to the episode. Use Automatic Context returns to following your work. Project and Working Context explains the controls.
On the web, open the Project button. Its Working on preview and Working Context summary are separate. Check the exact Story and Storyform references in the grid or saved Context card; the Context summary shows its saved name and source icons. The Working Context grid offers Story, Storyform, Persona, and Ideas. Conversation files stay with their conversation and are managed from its Context control.
For material already linked to the Project, you can also open Manage Project → Overview → Stories & Storyforms, open the resource, and choose Use in Working Context. Use Working Context applies the selection; Use and Save… continues into saving a named preset. Check the resulting Story and Storyform before continuing.
In an existing Narrova conversation, also inspect that conversation's Context. Its saved attachments can differ from the Project's current selection. Use the offered save or update action for Working Context, or Done for staged conversation attachments, then check the result. See Manage Context for save boundaries and exact controls.
Give each document a home
The place you save a document determines where it can be reused. A Project assembles linked work; it does not combine all of those resources into a single file library. Save the document with the Story, Storyform, or conversation that should use it.
| Save location | Use for | Where to manage it |
|---|---|---|
| Story Context | World rules, character biographies, research, series history, and tone guides. | The selected Story's Context Materials. |
| Storyform Context | One structural version's Throughlines, Storypoints, Storybeats, and draft material. | The selected Storyform's Context Materials. |
| Conversation Files | A one-off comparison or excerpt for the current discussion. | Files in that conversation's Context. |
Keep character files role-neutral when their function changes between Stories or structures. Put the Main Character assignment and other role-specific development with the Storyform that uses them. Give drafts and prior events clear version names so you can tell current material from background.
In the web Files tab, a file's three-dot menu offers Add to Story Context or Add to Storyform Context when the destination is available. These actions create a copy in the resource named by that file-copy control and leave the conversation file in place. Apply its intended Story or Storyform attachment first, then confirm the copy in that resource's Context Materials. This is a file-copy destination, not evidence that Narrova's independent Project save defaults changed. A Storyform opened in read-only reference mode cannot receive that copy.
For shared work, Write or admin access lets you manage Context files, including files uploaded by another collaborator. Notes access supports shared feedback rather than file management. Copying a conversation file requires Write or admin access to both its conversation and the destination Story or Storyform.
If an older file should no longer guide answers, hide it with an available visibility control or remove it from that library. Hiding keeps it stored in the same scope. Deleting a conversation file does not delete a separate Story or Storyform copy. See Files for readiness and inclusion details; native layouts can arrange these controls differently.
Keep conversations focused
Start a new conversation when the objective changes. Keep the intended work explicit and select the same Story and Storyform references when you want to reuse their lasting material. Check save destinations separately where offered; source selection does not file or move a transcript. Conversation files belong to a particular conversation and are not automatically copied into every new discussion.
When a conversation produces useful material, use Upload into Context where available to save its transcript with the intended Story or Storyform. The transcript becomes reference; uploading it does not turn every suggestion into an accepted structural choice. See conversation actions for branching, moving, and saving transcripts.
Continue in another workspace
Keep the same Story selected when changing how you work. Story Guide supports discovery; Story Expert and Storyform Builder develop structural choices; Narrova supports conversation; Subtxt develops the Storyform's Storytelling. Working Context carries the selected material into supported Workspaces, each of which checks whether it needs a Story or a Storyform.
Use Clear in the Context grid to clear narrative selections while keeping saved work. Clear Project removes the organizational selection while preserving compatible working material. Neither merges Stories, changes ownership, or rewrites every older conversation. See Choosing a Workspace for the handoffs.
Writing use: Keep a character biography with the Story, a role-specific interpretation with its Storyform, and today's scene excerpt in the conversation's Files. Choose Working Context for the task, then open the Workspace that helps you do it.