From Theory to Platform

Learn Dramatica

The canonical Dramatica model remains the foundation of the platform. The four Throughlines, the structural model, the Storyform, and the relationships among its Appreciations still describe the same complete narrative argument.

Thirty years of applying that theory—and building software around real writing workflows—also made new distinctions useful. Some are clearer names for relationships already present in Dramatica. Some are applied-theory concepts that turn structure into time and Storytelling. Others are platform systems that keep the work connected while you move between tools.

If You Remember The Original Application

Use this as the fastest translation map:

If you are looking for… You will find it in… What changed
Story Engine Settings Storyform Builder The Builder uses the current algorithms to navigate the same 32,768 complete Storyforms, with live option counts, inferred choices, locks, undo, examples, and direct NCP import/export.
Storyforming Storyform Builder or Subtxt → Forming Choose the Builder for direct structural control. Choose Subtxt when Storyforming is one phase of a larger development workflow.
The old development boxes Subtxt Forming, Illustrating, Plotting, and Writing preserve box-and-button precision while keeping every field attached to the same Storyform.
StoryWeaver by Melanie Anne Phillips Story Guide Develop ideas through guided writing, connected threads, and the Inspiration, Development, Exposition, and Storytelling stages.
The original Dramatica questionnaire Story Expert Work through structural questions with definitions, examples, written Storytelling, compatible possibilities, and Builder handoff.
Appreciations Storypoints Storypoint is the platform’s working term for a meaningful structural point such as Domain, Concern, Issue, Problem, Signpost, Driver, Limit, Outcome, or Judgment.
Plot Sequence Report Signposts, Progressions, Events, and Storybeats The platform turns temporal relationships into authorable beats at several scales instead of treating the report as a static final output.
Scene development Subtxt → Plotting → Moments A Moment can be a scene, sequence, chapter, or another author-defined unit. You weave Storybeats from the four Throughlines into it.
Character and player work Subtxt → Forming → Plot & Players / Character Arcs Players remain separate from the structural functions they perform, while arcs and Throughline relationships stay connected to the Storyform.
A saved Dramatica project file Storyform Context and NCP Storyform Context is the platform’s saved application state. Narrative Context Protocol carries structured story meaning between Narrova, Subtxt, Storyform Builder, and outside tools.
Help interpreting the model Narrova Narrova can explain and test a choice while reading the active Story, Storyform, uploaded material, and established development context.

The Vocabulary Added Around The Storyform

Perspectives

A Throughline is one of the four structural paths through a complete Storyform. A Perspective is the authored lens through which that Throughline is expressed in a particular story.

The distinction matters when a Throughline changes hands or contains several named viewpoints. The structural Throughline remains stable while one character’s Perspective can hand off to another. In the platform, use Perspectives to describe who carries the conflict and how that point of view appears in Storytelling.

Storypoints

Storypoint is the platform’s umbrella term for a structural Appreciation that carries meaning in the Storyform. Domains, Concerns, Issues, Problems, Dynamics, Signposts, and Plot Appreciations are all Storypoints.

The term makes an important workflow distinction visible: a Storypoint is the fixed structural meaning; its Illustration is the story-specific material you invent to express it. In Subtxt → Illustrating, work on the Illustration without confusing it for the underlying Storypoint.

Narrative Functions

Narrative Functions describe how pieces of the model operate in relation to one another. Where a Storypoint identifies a meaningful structural position, a Narrative Function helps explain what that position is doing inside a quad, circuit, character arrangement, or temporal progression.

This language is especially useful when the label alone does not explain the dramatic behavior. The platform can use Narrative Functions to turn a structural item into a more specific Storybeat or Dramatic Scenario without changing the item’s canonical meaning.

Storybeats And Dramatic Scenarios

Storybeats express the Storyform through time. They are not generic screenplay beats and they are not automatically scenes. A Storybeat is a meaningful unit of conflict within one Throughline; a scene may contain one Storybeat or many Storybeats from several Throughlines.

The platform develops a Storybeat as a Dramatic Scenario through three connected parts:

Together they turn abstract structure into something you can stage, draft, and revise without severing it from the Storyform.

Transits, Progressions, And Events

The platform exposes temporal structure at more than one scale. A Transit is the broad movement through a Signpost; Progressions divide that movement into smaller thematic turns; Events can develop those turns at a finer level. Each scale can carry its own Storybeats.

This is the modern working counterpart to reading a Plot Sequence Report as a static list. You can develop only as deeply as the story needs, then weave the resulting Storybeats into Moments without pretending that every structural turn must equal one scene.

Overviews

Overviews are short, story-facing summaries generated from established structural work. They include material such as a Logline, Genre Dynamics, Writing Style, Visual Design, Analysis Notes, and a Blended Throughlines Overview.

An Overview is orientation, not replacement structure. Use it to keep collaborators and later writing passes aligned, then return to the underlying Storypoints when an Overview starts drifting from the Storyform.

Moments And Story Weaving

A Moment is an author-defined container for Storytelling: a scene, sequence, chapter, set piece, or any other unit that makes sense for the work. Story Weaving is the act of arranging Storybeats from different Throughlines inside those Moments so the audience experiences one continuous story.

This separates meaning from presentation. Storybeats tell you which structural pressures must be expressed; Moments let you decide where those pressures meet on the page or screen.

Story Development And Interchange

The platform treats a story as living context rather than a single static file. Story Development records confirmed decisions, provisional ideas, open questions, Storyforms, conversations, and other durable creative state around a Story.

Narrative Context Protocol (NCP) is the interchange architecture used when that material needs to move between systems. NCP Core provides the neutral document envelope; the Dramatica Storyform Profile can carry Perspectives, Storypoints, Storybeats, Overviews, Players, Moments, and authored prose without making NCP itself the Storyform.

Story, Storyform Context, And Conversation Context

A Story holds the material you develop around a narrative, including its workbooks, documents, and attached Storyforms. Storyform Context holds a particular structural version and its development. Working Context selects the Story, Storyform, and Persona used for the task; a Narrova conversation also retains its own attachments and history.

A Project identifies what you are working on and organizes related Stories and Storyforms, goals, and activity. Working Context describes how you approach it through permitted reference material, Persona guidance, and Ideas. A solo writer usually uses the same Story and Storyform for both; a writing team may develop an episode while consulting series-wide references. Begin with a Story in its Individual Project, then broaden that organization when needed. Project Goals are organizational objectives; they do not start the autonomous Narrova Goals described below. Read What You Work On for the starting workflow and platform-specific save controls.

These layers answer different questions: What work am I developing? Which sources and guidance am I using? Where should accepted material be saved? Naming a reference Storyform does not make its choices accepted changes to another Storyform. Check the destination and saved result separately from the sources used to explore it.

Skills, Goals, Advisors, And Side Chats

These are execution tools rather than additions to Dramatica theory:

Use them to control how Narrova works. Continue to use the Storyform and confirmed Story Development state to control what remains true about the story.

Choose The Right Working Surface

A Practical First Pass For Experienced Dramatica Users

  1. Location: Storyform Builder. Action: Recreate a familiar Storyform using Dynamics and one Objective Story Domain, then inspect the inferred Storypoints and remaining Storyform count. Outcome: You see how the current Builder replaces Story Engine Settings while preserving the structural relationships you already know. Validation: The remaining count reaches 1 and the completed Storyform can be saved or exported as NCP.
  2. Location: Subtxt → Illustrating. Action: Open one Throughline, select a Storypoint, and write or refine its Illustration. Outcome: The fixed Appreciation stays separate from the story-specific expression. Validation: The Storypoint remains unchanged while the Illustration describes concrete conflict from the correct Perspective.
  3. Location: Subtxt → Plotting. Action: Create a Moment and attach Storybeats from the current Transit. Outcome: Structural beats from one or more Throughlines become an author-defined scene or sequence. Validation: The Moment shows the attached Storybeats and preserves their order within the allowed temporal boundary.

Writing use: Build one familiar story all the way from Storyform Builder to a single illustrated Storypoint and one woven Moment. That small round trip teaches the modern platform faster than trying to learn every module in isolation.

Common Translation Mistakes

Treating Storybeats As Generic Plot Beats

A Storybeat belongs to a Throughline and expresses part of the Storyform through time. Correction: identify its Perspective and structural source before deciding which scene will carry it.

Treating Moments As Structure

A Moment is Storytelling organization, not a new Storypoint. Correction: freely rename or reorganize Moments while protecting the Storybeats and temporal boundaries that give them meaning.

Treating Narrova As The Source Of Truth

Narrova can interpret, propose, and test, but a confident suggestion is not automatically an authorial commitment. Correction: confirm important decisions in the Storyform or Story Development state before allowing them to constrain later work.

Rebuilding The Same Story In Separate Tools

Starting disconnected copies causes drift. Correction: open Narrova, Subtxt, and Storyform Builder from the same Story or Storyform Context and use NCP when the work needs to travel outside the platform.

Continue Learning