Structuring Narrative Knowledge with StoryCode

Most creative tools treat story thinking as something loose, private, and disposable. Notes live in side documents. Research sits in folders. Character ideas float between drafts. Over time, the thinking that shaped a story becomes fragmented—hard to revisit, harder to reuse, and impossible to compound.

StoryCode™ was built to solve that problem.

At its core, StoryCode gives structure to narrative thinking without flattening it. It provides a system for organizing story elements, research, and conceptual work into a reusable narrative framework—one that evolves alongside your writing instead of being left behind by it.

This tutorial explains what StoryCode is, how it fits into Forme’s workflows, and how to use it to build a durable narrative system across projects and mediums.

What StoryCode Is (and Why It Exists)

StoryCode sits at a deliberate intersection: part narrative ontology, part knowledge system.

As a narrative ontology, StoryCode defines what kinds of things exist in a story: characters, themes, worlds, conflicts, relationships, references, and more. These elements are not just notes; they have meaning. A character is not the same as a theme. A setting is not the same as research. Each element represents a distinct role in narrative construction.

At the same time, StoryCode behaves like a knowledge system. It can house research, comps, historical context, tonal references, and abstract narrative thinking—anything that can be expressed in text and connected to your work. It is flexible, extensible, and designed to grow across drafts and projects.

This hybrid position is intentional. StoryCode gives you a strong default structure for thinking about story, while allowing you to reshape that structure over time. You are not locked into a prescribed worldview. You are given a foundation—and full control over how it evolves.

The result is narrative knowledge that can be revisited, refined, and reused instead of rewritten from scratch every time you start something new.

How Forme Parses StoryCode from Imported Drafts

When you import a screenplay or novel into Forme, StoryCode is generated through a structured analytical pass over the entire document. This is not a highlight system, a tag extractor, or a keyword scan. Forme reads the full work first, then identifies recurring, symbolically meaningful, or structurally significant narrative elements.

Only elements that meet that threshold are promoted into StoryCode.

This means StoryCode reflects story logic, not surface detail. One-off props, incidental locations, or throwaway dialogue do not appear unless they carry thematic, symbolic, or plot-level weight.

Once identified, these elements are written into a Library-level StoryCode document using Forme Markdown. That document becomes the canonical narrative knowledge base for the project.

The Structure of StoryCode

Every Library StoryCode follows the same top-level structure:

• # Story Elements contains all narrative components inferred from the draft
• # Research is reserved for external knowledge, references, comps, or contextual material added by the user

This separation is deliberate. StoryCode distinguishes between what the story is and what informs the story.

Story Elements: Component Parts and Hierarchy

Inside your Story Elements, Forme organizes narrative knowledge into a fixed second-level hierarchy. This hierarchy is what allows StoryCode to function as a narrative ontology rather than a flat notes page.

The default sections are:

• Themes
• Major Symbols
• Recurring Visual Motifs
• Plot Lines
• Laws of the World
• Characters
• Character Relationships
• Character Transformations
• Locations and Settings (Macro and Micro)
• Important Props
• Costume / Wardrobe / Aesthetic Details
• Time and Seasonality
• Narrative Voice & POV Techniques (novels)
• Cinematic Devices or Stylistic Techniques (screenplays)

Each section can contain zero or many Story Elements. Empty sections remain visible to signal intentional absence rather than omission.

This hierarchy is not cosmetic. It defines what kind of narrative object each entry is, which is why StoryCode can later be reused, analyzed, and extended safely.

Anatomy of a StoryCode Entry

Every Story Element follows a consistent structural pattern, but the content inside that structure is intentionally flexible.

In Forme Markdown, a Story Element begins like this:

## Themes

.Betrayal

The dot-prefixed name tells Forme that this is a discrete narrative object. From that point on, there is no single “correct” way to write the content of a StoryCode entry.

You can use:

• Long-form analytical prose
• Ordered or unordered lists
• A combination of paragraphs and lists
• Concise bullet points that evolve into deeper analysis over time

What matters is not the format, but the intent: each entry should capture narrative meaning, function, and relevance in a way that is useful to you.

For example, a Theme entry might begin as a short list of observations during early development, then expand into full analytical paragraphs as the story matures. A Plot Line might be expressed structurally, while a Symbol benefits from interpretive prose. StoryCode supports all of these approaches.

The only hard requirements are structural:

• Story Element Names are defined using dot-prefixed syntax (EX: .Forrest Gump)
• Each Story Element must remain clearly bounded from the next
• All Story Elements are attributed to the preceding ## Story Element Section (as shown above)

This balance—simple structure, flexible expression—is what allows StoryCode to function as both a narrative ontology and a living creative workspace.

How StoryCode Appears in the Library UI

In the Library’s StoryCode tab, the left-hand panel mirrors this hierarchy:

• Sections (Themes, Symbols, Plot Lines, etc.)
• Individual Story Elements nested underneath
• Clickable entries that jump to their full descriptions

The right-hand editor shows the full StoryCode document in Forme Markdown. Nothing is hidden. What you see is exactly what exists.

This transparency is intentional. StoryCode is not a locked system or an abstract layer. It is readable, editable narrative infrastructure.

Building and Extending Your Own StoryCode

The default StoryCode taxonomy is a starting point, not a limitation.

You can extend StoryCode in three ways:

Adding New Elements Within Existing Sections

You can add new .Story Element entries under any existing section at any time. These might include:

• additional themes
• secondary plot lines
• emerging motifs discovered during revision

Expanding Descriptions Over Time

StoryCode entries are not static. As drafts evolve, descriptions can deepen, shift emphasis, or reflect new interpretations.

StoryCode is designed to change alongside the work.

Creating Your Own Taxonomy

You are not locked into the provided hierarchy.

You can:

• add entirely new second-level sections
• rename sections to match your internal language
• create hybrid categories that reflect your creative process

StoryCode’s power comes from structure, not prescription. The system adapts to how you think about story.

Why Forme Enforces Structure Here

StoryCode’s formatting rules are strict for a reason.

Unstructured notes collapse over time. Tags lose meaning. Folders fragment context. StoryCode avoids these failures by enforcing:

• semantic clarity
• consistent hierarchy
• durable narrative objects

This is what allows StoryCode to persist across drafts, projects, and eventually AI workflows without becoming brittle or ambiguous.

How StoryCode Fits into Forme’s Core Workflows

StoryCode is not a separate feature you have to remember to use. It is woven directly into how Forme handles projects, starting from the moment a document enters the system.

Importing an Existing Screenplay or Novel

When you import a completed draft into Forme, you are prompted to link it to a Library. That Library becomes the narrative context for the project.

As part of the import flow, Forme parses the document and surfaces Story Elements into the StoryCode editor. These elements are automatically linked back to the source document, creating a clear relationship between the written work and the narrative thinking behind it.

From there, you can:

• Expand on existing elements
• Add new StoryCode entries that were never explicitly written into the draft
• Attach research, references, or conceptual notes that inform future revisions

The key point is that StoryCode does not replace your draft. It contextualizes it.

Creating a New Screenplay or Novel

When you create a new project inside Forme, a Library is created or selected at the same time. StoryCode becomes available immediately, even before a single page is written.

This allows you to:

• Define characters, worlds, and themes in advance
• Capture research and conceptual thinking as it emerges
• Let narrative structure develop in parallel with the draft itself

Whether you start with writing or with thinking, StoryCode remains the central place where narrative knowledge lives.

The StoryCode Taxonomy (and Its Flexibility)

Forme ships with a full StoryCode taxonomy designed to reflect how stories are actually developed across mediums. This taxonomy provides clarity and consistency, especially when projects grow in scope or complexity.

At the same time, it is not a constraint.

Every StoryCode element type can be extended, modified, or replaced. You can create your own taxonomy that reflects how you think about story. The default system is a starting point, not a ceiling.

Core Narrative Elements

StoryCode includes foundational story elements such as:

• Characters
• Relationships
• Themes
• World and setting
• Conflicts and stakes
• Motivations and goals

These elements capture the structural spine of a narrative and make implicit story logic explicit.

Structural and Conceptual Elements

Beyond traditional story components, StoryCode also supports:

• Acts, movements, or narrative phases
• Tonal and genre frameworks
• Symbolic or thematic motifs
• Perspective and point-of-view considerations

This allows StoryCode to reflect not just what happens, but how and why it happens.

Research, References, and Comps

Research is treated as first-class narrative thinking, not an external attachment.

You can store:

• Historical or technical research
• Cultural references
• Comparable films, books, or projects
• Market or audience insights

These elements can stand alone or be linked to narrative elements they inform, creating a traceable chain between research and story decisions.

Custom StoryCode Elements

If the default taxonomy does not reflect your process, you can create new StoryCode categories entirely.

This is where StoryCode shifts from a predefined ontology into a personalized narrative knowledge system. The structure adapts to your thinking—not the other way around.

StoryCode vs. Traditional Organization Systems

Most creative tools rely on flat organizational models:

• Folders for research
• Tags for categorization
• Freeform notes with no defined relationships

These approaches work for storage, but they break down when narrative thinking becomes complex. Tags don’t explain why something matters. Folders don’t express relationships. Notes become static snapshots instead of living systems.

StoryCode differs in three key ways:

• Semantic clarity: Each element has a defined narrative role.
• Relational structure: Elements can be connected meaningfully, not just grouped.
• Reusability: Narrative knowledge persists beyond a single draft or project.

Instead of managing information, you are modeling a story system.

StoryCode and AI: Present Behavior and Future Direction

It’s important to be precise about how StoryCode interacts with AI today—and how it will in the future.

As of now, StoryCode does not influence AI-generated output directly. StoryNotes, coverage, and other analyses are generated from the source document itself, not from the Library’s StoryCode.

This is intentional.

StoryCode currently functions as:

• A human-facing narrative system
• A durable context layer for your projects
• A way to structure thinking without altering analysis behavior

Beginning in early 2026, StoryCode will become part of Forme’s AI context engine. At that point:

• Only StoryCode within a linked Library will be included alongside a source document
• Structured narrative context will inform analysis and generation
• AI outputs will reflect the story logic you’ve already defined

This phased approach ensures that StoryCode is useful on its own first—before it becomes computationally powerful.

Using StoryCode as a Long-Term Narrative System

The real value of StoryCode emerges over time.

As you move between drafts, projects, and even mediums, StoryCode allows narrative thinking to accumulate rather than reset. Characters evolve. Themes deepen. Research compounds. What you learn in one project can inform the next without being re-invented.

StoryCode is not a productivity trick. It is infrastructure for creative thinking.

By structuring narrative knowledge intentionally, you gain clarity, continuity, and leverage—across stories, across formats, and across your entire body of work.

That is the promise of StoryCode.