Subtxt/Dramatica®

Appearance

Context ​

Narrova supports your creativity by offering three distinct kinds of context:

  • Story Context – Broad, foundational content relevant across multiple Storyforms or early‑stage story development.
  • Storyform Context – Structured narrative analysis tied to a specific Storyform guided by Dramatica theory.
  • Conversation Context – Immediate, focused context for a single Narrova interaction.

Story Context is your go‑to place for broad, foundational content relevant across multiple Storyforms or during early‑stage story development. Store general character outlines, world‑building notes, thematic explorations, research docs, mood boards, and inspirational images. These act as universal references across Storyforms until you’re ready to commit details to structure.

Storyform Context is your organizational hub when you’re ready to work with a precise narrative structure. Documents and images here are intentionally linked to a specific Storyform—your thematic, character, and plot blueprint. Use it for character arcs, scene breakdowns, visual references tied to narrative elements, and any material that sharpens a particular Storyform.

Conversation Context is immediate and ad‑hoc. Upload files directly into a conversation when you need short‑lived, session‑specific context—script excerpts, brainstorm notes, scene feedback, or targeted thematic queries.

By clearly distinguishing between these three, Narrova helps you organize and streamline your creative workflow—whether you’re exploring, locking structure, or refining specific beats.

What’s new in Context ​

We’ve clarified the difference between Story Context and Storyform Context and added more freedom to move and manage both:

  • New Stories navigation: jump directly to Story Context (Stories) or Storyform Context (Storyforms). (screenshot: Stories menu)
  • New Storyforms index: browse all Storyforms in one place and open any of them instantly. (screenshot: Storyforms index)
  • Clearer actions on Storyforms inside a Story: Move to Story, Detach from Story, or Delete—with explicit confirmations. (screenshots: overflow menu, delete confirmation)
  • Data safety: Deleting a Story or Storyform Context does not delete your conversations; it only removes their association with that context.

Setting the Context ​

Narrova shows the current context via the Context Switcher at the bottom of the input panel. Tap Context to toggle sources on/off and guide your creative process.

Icons

  • Open book → Story context
  • Atom → Storyform context
  • Chat → Conversation context

If more than one icon is visible, you’re actively working with multiple contexts (e.g., Story + Storyform).

INFO

Limit: You can set at most two contexts simultaneously. For example, you can set a Story context and upload files into the Conversation (Story + Conversation). If both Story and Storyform are set and you need to add more files, upload them to Story → Documents or Storyform → Documents so they’re included as context.

Organizing Context ​

Organizing Context is where you manage your Stories and the Storyforms attached to them. Open it anytime via the Stories link in the top navigation.

Stories menu & context indexes ​

  • Click Stories in the top nav to open the menu. (screenshot: Stories menu)
  • Choose Story Context to go to the Stories index.
  • Choose Storyform Context to go to the Storyforms index (a global list of all your Storyforms). (screenshot: Storyforms index)

Stories index (Story Context) ​

A clean overview of everything you’re building:

  • Title – clear, searchable project names
  • Last Updated – recent activity at a glance
  • Filters & sort – find active drafts, archived items, or recent work fast

Create a Story: click Create Story, add a title or quick prompt, and choose how to begin (e.g., StoryGuide or Unspool).

Storyforms index (Storyform Context) ​

Browse every Storyform you’ve created—no matter which Story it’s attached to. From here you can:

  • Open a Storyform directly.
  • Create New Storyform in Storyform Builder to start a new structure.

Inside a Story ​

Selecting a Story opens its context hub—documents, conversations, and structure in one place.

Context Documents (Story → Documents) ​

Upload any references you want Narrova to consider for this Story only (research, notes, transcripts, outlines).

  • Upload Documents: add files that ground Narrova’s answers
  • Manage: rename or remove to keep things clean
  • Scoped: used only within this Story’s context

Conversations ​

Your running narrative threads with Narrova:

  • See titles and timestamps for quick orientation
  • Jump back into any thread to continue where you left off
  • Pin key threads you’ll revisit often

Storyforms (attached to a Story) ​

Attach, validate, and manage structure as it emerges:

  • Attach / create a Storyform when you’re ready
  • Validate to ensure consistency before development
  • Set Primary if you explore variations

Storyform actions (… menu) (screenshot: overflow menu)

  • Move to Story – Re‑home the Storyform under another Story. When you move a Storyform, that Storyform and all of its conversations are associated with the destination Story.
  • Detach from Story – Break the link between the Story and the Storyform. The Storyform remains available in the Storyforms index for reuse.
  • Delete – Permanently delete the Storyform. You’ll be asked to type the title to confirm. Deleting a Storyform removes all documents uploaded to it and cannot be undone.

Important: Deleting a Story or Storyform Context does not delete conversations. Those conversations remain but lose that context. If you don’t want them anymore, delete the conversations manually from your conversation list.

Tip: Start loose with StoryGuide to shape a working thesis. When it clicks, attach a Storyform and continue refining.

Switch to Subtxt ​

Prefer less chatbot, more structure? Subtxt is the programmatic, panel‑based interface—fields, forms, and clear controls—for precise story work. Dive in when you want to lock structure and manipulate the exact levers of your narrative.

Use Subtxt to:

  • Define and manage your Storyform with explicit fields
  • Set Signposts, Drivers, Progressions, and Storybeats with clarity
  • Map characters and elements without ambiguity
  • Keep things organized as you iterate, version, and refine

Until unified, open Subtxt here: subtxt.app.

Moving Conversations into Different Contexts ​

To move a conversation’s association, click the three‑dot (… ) menu in the upper‑right of the conversation panel. Choose an existing Story, Storyform, or Conversation context—or create a new one inline. This keeps your dialogue in the right place as your project evolves.

A Note about Memory ​

While cross‑conversation memory is on the roadmap, it isn’t enabled by default. Too much memory can be reductive. In Narrova, the Storyform acts as “story memory.” Even when conversations are separate, the Storyform preserves coherence and intent across sessions.

Managing Conversation Context ​

TL;DR (spiky): Don’t cram a mega‑novel into one chat. Let the Storyform be your spine, and use focused conversations for single facets. Upload prior chats as Story → Documents or Storyform → Documents, then work in small, sharp passes. The Storyform keeps everything resonant.

Why this matters ​

Large context windows are powerful but finite. A single, ever‑growing chat becomes brittle, slow, and hard to reason about. Narrova works with limits by treating the Storyform as persistent foundation and your Documents as reusable memory.

Fact check (Aug 2025): The model context window is capped by OpenAI. GPT‑4.1 supports up to ~1M tokens; GPT‑5 supports up to ~400k tokens. Plans (including Infinite) don’t change model hard limits. (Numbers may evolve.)

What persists between conversations ​

Retained automatically

  • Your Story and Storyform
  • Any files in Story → Documents or Storyform → Documents

Not retained by default

  • Ad‑hoc “remember this” in old chats
  • Snippets not saved into Documents

Rule of thumb: If it matters later, move it into a Document tied to the Story (or Storyform).

  1. Collect & upload

    • Upload prior chats, chapters, and research into Story → Documents; Storyform‑specific materials into Storyform → Documents.
    • Prefer small, single‑purpose docs (e.g., MC Bio, Canon Facts, Glossary, Ch1–Ch3 Draft).

  2. Work in focused conversations

    • Open a new chat per focus area (e.g., MC Throughline, Costs & Dividends, Relationship Story).
    • Reference only the docs you need by title.

  3. Let the Storyform keep coherence

    • Each focused chat still harmonizes with the rest because the Storyform anchors choices.

  4. Iterate & consolidate

    • When a chat produces something keepable, save the output back into a Document with a short changelog.

Setup: Organizing your Documents ​

Use a simple taxonomy:

  • Canon Facts (world bible)
  • Character Sheets (MC, OC, RS pairings)
  • Throughline Workpads (OS, MC, OC, RS)
  • Method & Mechanics (Costs, Dividends, Requirements, Prerequisites)
  • Drafts (scene packs or chapter tranches)
  • Glossary (terms, spellings, style notes)

Chunking tip: 2k–10k tokens per doc (≈ 5–30 pages) is a sweet spot.

Working in focused conversations ​

Start a new chat with a tight objective, attach/reference the relevant docs by title, and speak in outcomes.

Example prompts

  • MC Throughline: “Using MC Bio, Canon Facts, and the current Storyform, refine the MC Throughline: Problem/Approach, Signposts & Journeys. Flag contradictions with OS.”
  • Costs & Dividends: “With Canon Facts and Method—Costs & Dividends, propose 3 viable Cost/Dividend pairings that amplify the MC issue. Justify each against the Storyform.”
  • Relationship Story: “From RS Notes + Glossary, generate 6 scene‑level beats (conflict first) that escalate RS tension. Map each beat to its Storybeat.”

Save it back

  • Paste approved results into a Document (e.g., MC Throughline—v2) with a one‑paragraph changelog.

Troubleshooting & pro tips ​

  • Hitting token limits? Trim attached docs to only what you need now; summarize bulky sources into a short Working Notes doc.
  • Cross‑chat drift? “Audit MC Throughline—v2 against the current Storyform. List mismatches and fix.” Save results.
  • Doc sprawl? Adopt prefixes: CF_ (Canon Facts), RS_, OS_, MC_, OC_, DRAFT_, GLOSS_.
  • Version control: Suffix with dates or v‑numbers: MC_Throughline_v3_2025‑08‑14.
  • Signal intent: Start prompts with verbs: Refine, Audit, Synthesize, Contrast, Sequence, Storyboard.

Quick checklist ​

  • [ ] Prior chats & files uploaded to Story → Documents (or Storyform → Documents as appropriate)
  • [ ] Docs chunked by purpose; sensible prefixes
  • [ ] One focused chat per facet
  • [ ] Explicit references to the docs you need
  • [ ] Results saved back into Documents with a short changelog
  • [ ] Using Stories menu to jump between Stories and Storyforms
  • [ ] Move/Detach/Delete Storyforms as needed; remember that deleting a Story or Storyform does not delete conversations