Dramatica

Appearance

Dynamics ​

Dynamics are the high-level Storyform commitments that determine how a story moves, what kind of pressure it applies, and what emotional verdict it leaves behind. In plain language, they tell you whether the story changes or holds, what drives events forward, how the ending resolves, and whether that resolution feels worthwhile.

Unlike Perspectives, Dynamics do not describe a point of view inside a Throughline. They describe the global shape of the Storyform itself.

Concept ​

In Dramatica, Dynamics are binary structural choices. They answer questions like:

  • Does the Main Character Change or remain Steadfast?
  • Does the story push toward Start or Stop?
  • Is the pressure driven by Action or Decision?
  • Does the story end in Success or Failure?
  • Does that ending feel Good or Bad?

These are not local illustrations. They are story-wide commitments. Once chosen, they influence how the entire Storyform is interpreted.

Why It Matters ​

Dynamics are easy to underestimate because they look simple. But they are some of the most consequential choices in the Storyform. They shape the audience's experience of change, judgment, escalation, and closure.

If your Dynamics are off, the story can feel confused even when the scenes themselves seem strong. You may have a compelling sequence of events, but the argument underneath those events will drift.

Writing use: treat Dynamics as the story's governing conditions, not as optional labels to fill in later.

Character Dynamics ​

Character Dynamics define how the Main Character's personal pressure works:

  • Resolve — Change or Steadfast
  • Growth — Start or Stop
  • Approach — Do-er or Be-er
  • Problem-Solving Style — Linear or Holistic

These are personal and audience-facing, but they are still Storyform-level commitments. They are not separate Perspectives. They describe the kind of pressure shaping the Main Character's journey.

Story Dynamics ​

Story Dynamics define how the larger story resolves:

  • Story Driver — Action or Decision
  • Story Limit — Optionlock or Timelock
  • Outcome — Success or Failure
  • Judgment — Good or Bad

Together, these Dynamics answer the audience's final structural question: did the effort work, and did it feel worth it?

Why Dynamics Do Not Have Perspectives ​

This is the key distinction:

  • A Perspective belongs to a Throughline.
  • A Dynamic belongs to the Storyform.

Perspectives tell you where conflict is being experienced or interpreted: Objective Story, Main Character, Influence Character, or Relationship Story. Storypoints and Storybeats can be attached to Perspectives because they are Throughline-specific expressions of conflict.

Dynamics work differently. They are not containers for conflict within a particular point of view. They are structural settings that govern how the full story behaves.

For example, Story Outcome is not an Objective Story Perspective. It is a global verdict on whether the story's effort ends in Success or Failure. That result affects how you understand the whole argument, but it is not itself a Throughline-specific viewpoint.

The same logic applies to Judgment, Driver, Limit, and the Character Dynamics. They color and constrain the Storyform, but they are not separate lenses through which the audience experiences conflict.

IMPORTANT

Do not assign Perspectives to Dynamics. If you do, you blur the line between global structural settings and Throughline-specific conflict.

In The Platform ​

Forming ​

  • Location: Subtxt -> Forming
  • Action: Set the Character Dynamics and Story Dynamics in the Storyform controls.
  • Outcome: The platform locks the emotional and structural conditions of the Storyform.
  • Validation: Related Storyform choices, summaries, and downstream prompts reflect the selected Dynamics.

Illustrating ​

  • Location: Subtxt -> Illustrating
  • Action: Use the current Dynamics to evaluate whether Storypoints and Storybeats feel structurally honest.
  • Outcome: Your illustrations stay aligned to the selected Resolve, Driver, Outcome, and Judgment.
  • Validation: Beats read as expressions of the chosen Storyform rather than as isolated dramatic ideas.

Narrova ​

  • Location: Narrova -> Storyform or Throughline workflows
  • Action: Ask Narrova to test alternatives while keeping the current Dynamics intact.
  • Outcome: Narrova proposes aligned revisions instead of drifting into a different Storyform.
  • Validation: Suggested changes preserve the same ending logic and emotional promise unless you explicitly change the Dynamics.

Common Mistakes ​

Treating a Dynamic like a Perspective ​

This is the most common error. If you think “Story Outcome must belong to the Objective Story Perspective,” you are mixing global structure with Throughline viewpoint.

Correction: keep Outcome at the Storyform level. Then ask how each Throughline illustrates the consequences of that Outcome.

Treating Dynamics as optional labels ​

Writers sometimes leave Dynamics vague because they seem like finishing touches. They are not. They control how the Storyform reads.

Correction: choose them early enough that they can guide your Storypoints, Throughlines, and ending pressure.

Using Dynamics as scene instructions ​

A Dynamic is not a scene beat. “Action Driver” does not tell you what happens in the next scene. It tells you what kind of event forces major turns across the story.

Correction: use Dynamics to evaluate sequences, not to replace Storybeats.

Practical Interpretation ​

Here is the clean way to think about the relationship:

  • Perspectives tell you where conflict is viewed.
  • Storypoints tell you what that conflict is about.
  • Storybeats tell you how that conflict unfolds in time.
  • Dynamics tell you what overall shape the argument takes.

That separation is what keeps Dramatica coherent. Once you collapse Dynamics into Perspectives, the model starts to lose the difference between structure and expression.

Next Step ​

After setting your Dynamics, move to Perspectives and Storypoints. Use those to express how each Throughline experiences the pressure created by the Storyform's global Dynamics.