Story Development

Story Development is the living record of what has been established, what remains provisional, and what still needs attention across a Story. Its editable Story Development Ledger gathers durable creative state from Narrova conversations, Goals, Memory citations, Story Guide work, Storyforms, documents, and your own entries.

In plain language: conversations are where you work; Story Development is where you see what the work has added up to.

Why Story Development matters

Story development is nonlinear. Writers explore, reject, return, reframe, encode, draft, and revise. A rigid checklist cannot represent that movement, but a pile of transcripts cannot reliably show the current truth either.

Story Development keeps the useful middle layer: confirmed commitments, provisional assumptions, unresolved questions, validation needs, changes, and writer-owned decisions. It is broader than a Storyform and more selective than a transcript.

Writing use: Open Story Development before beginning a new phase so you can see the current state without rereading every conversation.

Enable Story Development

The Story Development Ledger is currently available as an experimental feature.

Open Story Development

Location: Narrova → Composer controls.

Action: Select Develop.

Outcome: Story Development opens in a right-hand panel for the active Story. Select Story Development in the panel header to open the full page.

Validation: The page title shows the Story, and the surface includes the Story Development Ledger plus any available Current State, Memory Citations, Goals, Story Components, Storyform Components, or conversations.

If the conversation has no Story Context, enter a Story title in Start Story Development and select Create Story. Narrova creates the Story Context and opens its empty development state.

Understand the Story Development Ledger

The Ledger is an editable Markdown report that organizes the Story's durable development state. It is a projection of the current records, not a replacement for the underlying Storyform, documents, conversations, or Memory entries.

The Ledger may include:

The page describes this as “a living set of story notes.” That is the right mental model: enough structure to preserve direction, without pretending story development moves through one fixed pipeline.

Edit and download the Ledger

Location: Story Development → Story Development Ledger.

Action: Edit the Markdown directly. Changes save after you pause typing and again when the editor loses focus.

Outcome: Your organized Ledger wording becomes the saved Story Development report for the Story.

Validation: Watch the save state and Last saved time. Navigate away, return, and confirm that the edit remains.

Select Download to export the current Ledger as Markdown.

Team members with read-only access can inspect and download Story Development, but they cannot edit the Ledger, add items, change statuses, or rename the Story.

Add and manage Ledger items

Select Add Item to record a durable piece of development state.

An item includes a type, title, summary, and optional phase. Types organize entries into useful sections such as commitments, questions, assumptions, validation, or history. Narrova provides starter artifact types, and writers can create private types when a Story needs a different category.

After an item exists, open it to edit its wording or phase. Use the visible status actions to confirm or retire it.

Validation: The item appears in its Ledger section with the expected status, ownership, and source label.

Writing use: Record decisions that should constrain future work, questions that must remain visible, and rejected directions you do not want Narrova to resurrect.

Read Current State and Memory Citations

Current State gathers landed material from the Story's connected surfaces. It helps answer “What is true or active right now?” without asking you to infer that state from several menus.

Memory Citations show durable Narrova memories associated with the Story. Each citation can include its scope, status, summary, memory type, and source lines. Use these citations to inspect what Narrova carried forward and to identify memories that need correction.

If a memory is wrong, tell Narrova exactly what changed and which scope should own the correction. Prefer revising or superseding an old decision to erasing the fact that the Story changed intentionally.

Review Goals, Storyforms, and Story Guide work

Story Development can bring several development surfaces together:

These sections are references, not a command to follow a fixed order. Move between discovery, Storyforming, Encoding, Storyweaving, Reception, drafting, and repair according to what the Story needs.

Discuss Story Development with Narrova

Several Story Development cards can start a Story-aware Narrova conversation. Use Discuss notes, Open in Narrova, a Start From This State prompt, a Dramatica Tip, or another available action.

Outcome: Narrova opens with the Story attached and a prompt grounded in the selected development material.

Validation: The new conversation identifies the Story and addresses the selected item rather than responding with a generic brainstorm.

Annotate several items at once

On the full Story Development page:

  1. Select Annotate.
  2. Choose a Ledger item, Memory citation, Goal, Story Component, Dramatica Tip, or other supported card.
  3. Add a concrete editorial note.
  4. Repeat for the other items you want to address.
  5. Select Send to Narrova.

Outcome: Narrova receives the annotations as an ordered, Story-grounded development request.

Validation: The new conversation names the selected material and works through your notes in order.

Move between Narrova, Subtxt, and Storyform Builder

The full Story Development page provides direct paths to the major working surfaces:

Use Story Development as the overview, then move to the surface that owns the next concrete action.

Common mistakes

Treating the Ledger as a linear production checklist

The Ledger records state; it does not force Storyforming, Encoding, Storyweaving, and Reception into one rigid sequence. Follow the Story's actual needs.

Saving every interesting sentence

Durable state should change what future work needs to know. Keep transient brainstorms in the conversation or a Note until they become a commitment, open question, constraint, or useful record of change.

Letting Narrova guesses outrank writer decisions

Check ownership and status. Confirm the material you accept, correct the material you reject, and keep unresolved interpretations provisional.

Editing the report but ignoring the underlying source

The Markdown report helps organize the Story, but Storyforms, files, Memory entries, and conversations remain their own records. Update the owning surface when the underlying fact itself must change.

Story Development is empty

Confirm that the conversation has the intended Story Context. Then add one durable item or start a focused Narrova pass from Start with one useful move.

A practical Story Development rhythm

  1. Open Develop at the start of a work session.
  2. Review Current State, open questions, needs-review items, and active Goals.
  3. Choose one concrete next move.
  4. Work in Narrova, Subtxt, or Storyform Builder.
  5. Confirm accepted decisions and retire rejected directions.
  6. Edit the Ledger summary so the living notes remain readable.
  7. Download the Markdown report when you need a portable checkpoint.

Validation: A returning writer should be able to explain what is settled, what is uncertain, and what to do next without rereading the full conversation history.