Forme treats Libraries as a foundational part of modern longform writing—not an optional organizational aid. Every screenplay, novel, or related document exists within a broader narrative system, and Forme is designed to make that system explicit from the moment a document enters the platform.
This tutorial explains how the Library Dashboard works, why document linking is required by default, and how Libraries function as long-term narrative infrastructure for projects of any size—single works, collaborative slates, or multi-project story universes.
Why Libraries Are Required in Forme
In Forme, writing does not happen in isolation. Scripts and manuscripts generate feedback, spawn development artifacts, and evolve across drafts and formats. Libraries exist to ensure those relationships are preserved rather than fragmented.
When you import a document, Forme automatically:
- Parses the material into structured Story Elements
- Places those elements into the StoryCode Editor
- Links the source document to a Library alongside any generated outputs
When you create a new screenplay or novel, Forme requires that you either:
- Create a new Library automatically linked to the source document, or
- Select an existing Library to link the document into
This is not a restriction for its own sake. It is a deliberate design choice that establishes document linking as the baseline workflow, not an advanced feature to be discovered later.
While any linked document can be unlinked after the fact, every entry point into Forme begins with a Library because narrative systems are more durable—and more useful—than standalone files.
What the Library Dashboard Actually Does
The Library Dashboard is a relationship manager, not a storage layer. Documents remain independent, editable assets. The Library defines how they relate to one another.
Within a Library, you can:
- See all documents linked to the same narrative context
- Add or remove existing documents without modifying their contents
- Maintain continuity between source drafts and derived materials
- Anchor StoryCode so narrative logic persists across assets
The dashboard does not ask you to reorganize your work. It simply ensures that everything related to a story knows it belongs together.
This is why Libraries scale cleanly as projects grow.
Libraries as the Starting Point for Single Projects
For many writers, a Library supports one primary work. In these cases, the Library acts as a narrative spine rather than a container.
A single-project Library typically links:
- A source document (the core screenplay or manuscript)
- StoryNotes associated with the source doc
- A StoryDeck
- A query letter
Because Story Elements are parsed at import time, the Library for an imported source doc immediately reflects the story’s internal structure. As drafts evolve and new documents are added, that structure remains stable—even when individual files change.
This allows writers to revise aggressively without losing narrative coherence across materials. The Library absorbs change without fragmenting context.
Libraries for Multi-Project and Universe-Level Work
For producers and teams managing multiple works, Libraries function at a higher level.
A single Library may link:
- Multiple scripts or manuscripts
- Parallel drafts or alternate versions
- Assets tied to sequels, spinoffs, or adaptations
- Supporting documents across development phases
In this mode, the Library represents a story system, not a project. Documents enter and exit over time, but the underlying narrative logic persists.
Because linking is enforced at creation and import, no document enters the system without being grounded in context. This prevents the slow erosion of institutional knowledge that often occurs when projects span years or teams.
Role-Specific Use of the Library Dashboard
Libraries are structurally neutral, but different roles extract different value from them.
Screenwriters
Screenwriters benefit from Libraries as continuity anchors. Notes, revisions, and development artifacts remain aligned as the script changes. The Library reduces re-explanation and keeps feedback grounded in the same story logic over time.
Novelists
Novelists often use Libraries to manage longer arcs. A Library may support a manuscript, adaptation analysis, and future development documents simultaneously. This allows prose-first creators to explore new formats without resetting narrative context.
Producers
Producers use Libraries as organizational intelligence. By linking all relevant materials—without editing them—the Library becomes a shared reference that stabilizes development, packaging, and collaboration across stakeholders.
In every case, the Library exists to outlast any single document.
Linking Is the Default—Unlinking Is the Exception
Forme encourages document linking not through persuasion, but through structure. Importing and creating always result in a linked document because narrative work benefits from continuity by default.
That said, Libraries are not prisons. Any document can be unlinked later. The system simply assumes that connection is more useful than isolation unless proven otherwise.
This philosophy reflects how longform creative work actually behaves in the modern era: iterative, cross-format, and increasingly collaborative.
Libraries as Narrative Infrastructure
Libraries are designed to persist. Drafts change. Feedback evolves. Projects expand or pause. The Library remains.
Because Libraries link rather than contain:
- Documents can be replaced without breaking context
- New materials can be added at any stage
- Older assets can be removed without destabilizing the system
Over time, Libraries become narrative infrastructure—quiet, durable, and essential.
Libraries as the Context Engine for Future AI Workflows
Libraries are not only organizational infrastructure—they define how Forme's AI understands story at scale.
Beginning in early 2026, Forme will introduce the ability to include a Library alongside a source document in AI generative tasks. In this model, the StoryCode housed in the Library will be used as shared context—providing structured narrative intelligence without reprocessing or merging full documents.
When generating StoryNotes or creating asset documents, Forme’s AI will:
- Analyze the selected source document directly
- Reference the Library’s StoryCode to understand story logic, canon, and continuity
- Ignore the full text of other linked documents
This approach preserves clarity and control. StoryCode acts as the authoritative narrative layer, while individual documents remain discrete, editable artifacts. The result is deeper, more consistent analysis and generation—without collapsing multiple drafts or assets into a single, opaque input.
Because Libraries already enforce StoryCode parsing and document linking at import and creation time, this capability extends the existing system rather than changing it. The relationships you establish today become structured context tomorrow.
Libraries are not merely memory banks for documents. They are engines for narrative intelligence.
Libraries as the Default State of Creative Work
Forme requires Libraries because longform storytelling has outgrown the standalone file. Stories now live across drafts, formats, and artifacts, and meaningful creative work depends on preserving those relationships.
The Library Dashboard is how Forme enforces that philosophy without adding friction. Every document enters with context. Every project begins connected.
That’s not organization as an afterthought. That’s organization as a creative baseline.
