Breaking Down Storybeats & Story Encoding

Surprise livestream going over how you can break down Storybeats like Signposts into Progressions and Events. Also, a good primer on Story Encoding and trying out alternate ideas for your stories:

Unlock the next level of storytelling with Narrova | Livestream: Breaking Down Storybeats & Story Encoding. In this session, we’ll explore how you can quickly spin up different takes on your story while staying anchored to the original Storyform. Discover how Narrova now breaks down Act-sized Storybeats—known as Signposts—into richer layers of Progressions and Events, giving you more detail and flexibility than ever before. Whether you’re testing new directions or deepening your narrative, this livestream will show you how Narrova helps keep every version of your story structurally sound.

Hello Jim,

Thank you very much for sharing the video about “Breaking Down Storybeats & Story Encoding.”

I have two questions about it:

Question 1) I’ve been familiar with Dramatica since the 90s. What has never been entirely clear to me is how Dramatica sorts the order of the respective signposts and why it has to be in that exact order.

I still have the old Dramatica v4.0 on my computer. I transferred so many elements from your James Bond story form until Dramatica was on ONE story form. The elements filled in by Dramatica corresponded exactly to your story form.

However, where the whole thing differs is in the order of the signposts in all 4 throughlines.

For the MC Throughline, Dramatica gave me the following order:

Signpost 1: Progress

Signpost 2: Present

Signpost 3: Future

Signpost 4: Past

Your story form has the following order for the MC Throughline:

Signpost 1: Past

Signpost 2: Progress

Signpost 3: Present

Signpost 4: Future

Is there a different mathematical basis behind Narrova?

Are there new rules?

Am I thinking incorrectly?

Question 2) When Narrova first proposes the progressions, they are:

Knowledge - Ability - Desire - Thought

You then explain that the progressions are from a completely different place, namely from the Psychology Domain under the Signpost Being. I find exactly the same thing in Dramatica 4.0 in the Theme Browser.

Then you tell Narrova to please work with the story form and not fantasize too much.

Narrova looks at the story form and then comes up with exactly the same progressions:

Knowledge - Ability - Desire - Thought

These are still from a completely different place, namely from the Psychology Domain under the Signpost Being.

So, from my point of view, nothing has changed.

Why are the same progressions suddenly correct now?

I hope these questions aren’t too nonsensical :wink:

Best regards,

Uwe

This is a fantastic question!

Everyone asks it eventually, so more than happy to answer it for you so you can gain greater clarity.

To be clear with the example found in the video, when I broke down Signpost 1 of the Past many would have assumed that the children elements of Fate, Prediction, Interdiction, and Destiny would show up. They didn’t - the children Elements of Being showed up. Why is that?

Why do Elements end up “out-of-place”?

In short, the model of the Storymind that you see as those large towers (the PDF and in the Theory book) illustrate the model at rest. Every Element is perfectly in balance (Universe against Mind, Past against Memory, etc.). You can think of it as a visual representation of a Zen state of mind, where there is no inequity and no imbalance.

Once you introduce an imbalance, and the Storymind identifies a Problem, everything in the model gets wound up through a combination of flips and rotates. You can think of the model like a Rubik’s cube, where the model at rest version has all the colors aligned perfectly on either side. Once the Storymind identifies a Problem (i.e., when you create a story), the cube gets wound up over and over again, until–at the beginning of the story–every color is out of place. This inequity expresses itself as narrative tension–the mind wants to see everything back at rest. A story is simply a re-arranging of those tiles back to equity.

During that process of winding up the model, Elements will fall out of place with their at-rest parent Elements. In the example above the children Elements of Being (Knowledge, Ability, Desire, and Thought) end up under Past in the MC Throughline. This is a function of both Dynamics (Resolve, Growth, etc.) and Throughline arrangements–these items tell the platform how to wind up the model to achieve the right kind of narrative tension prior to a story beginning. This distortion is in part, a method of modeling projection in the Storymind (i.e., it’s not my problem, it’s yours).

Practically speaking, you’ll find these out-of-sorts combinations more conducive to narrative to tension and conflict. In other words, how much more fun is it to write about the past in terms of what you know, what you’re capable of doing, what you long for, and what you or others think of your past? Now, compare that to the at-rest version of writing about the Past in terms of Fate, Prediction, Interdiction, and Destiny…definitely, not as compelling.

Differences between earlier Dramatica applications and the Subtxt/Dramatica platform

Narrova is part of the Subtxt/Dramatica platform–which means that it is build on top of the Subtxt Narrative Engine–not the original Dramatica engine. While building Subtxt, I identified two problematic issues with the original algorithms that I updated and engineered into the justification process found within the Subtxt application. The result of this is that many, if not all, of the Storyforms found in Subtxt do not align with the earlier Dramatica application, particularly when you get down to the Progressions and Events beneath the Signposts.

Many familiar with Dramatica and Subtxt find the newer plot progressions to be more accurate and more intuitive when it comes to the order of events within their story.

Now that we have the Storyform Builder within the platform, it becomes necessary to get everyone on the same page with the updated algorithms–which I am, coincidentally enough, preparing today!

Once this is complete, I will be re-visiting my own engineering of the justification process back in 2021. I’m fairly confident that I’ll be able to speed up the process so that you won’t have to wait ten minutes for a Storyform that hasn’t been built yet on the platform.

Let me know if you have any follow-ups. Dramatica co-creator Chris Huntley addressed the reason why the model does what it does here back in 2017: How does Dramatica determine Signpost order? - #15 by chuntley

Wow! That was a very quick, detailed, and very understandable answer.

Thank you very much for that.

The image with the Rubik’s Cube is very helpful in visualizing what happens.

I find the original model on which Dramatica is based incredibly complex. I find it fascinating that you have developed it further, but at the same time, it’s almost too advanced for me. But it’s great.

Thank you for doing what you do. May the stories that result from it all become a little better and reach many people.

Best regards,

Uwe

1 Like

I’ve updated the docs to include everything added/extended with Subtxt in regards to Storybeats: Storybeats | Subtxt/Dramatica®

here are all your prompts from the session

storyencoding: lets say the MC Throughline is all about James Bond - make up something for his Domain and Concern, and then breakdown the first Signpost into the four Progressions using your breakdown tool

continue for signposts 3 and 4

so if you were to describe both his Domain and Concern and why they are a problem for him in this story personally - how would you explain it

I feel like I’ve seen this before - what are five other options for this Domain/Concern for a brand new take on the Bond franchise

oh! lets go with #2 - go ahead and rewrite all signposts and progressions with all of that in mind

thats really great - my producer wants to see both versions - this latest cool one; and the one before - can you write up both in an engaging one-page executive summary (one-page for each)

1 Like

Thank you so much for this! I’ve gone ahead and added them to the documentation here: Working with Narrova | Subtxt/Dramatica®