# PlotDirector Plot Lines Redesign Specification ## Purpose The primary purpose of Plot Lines within PlotDirector is not simply to visualise story structure. The core purpose is to: - Track narrative promises made to the reader. - Prevent important plot threads from being forgotten. - Ensure all major story threads receive appropriate payoff. - Help authors identify unresolved, neglected, abandoned, or weak plot lines. - Provide a visual representation of how the story evolves over time. Visualisation is important, but it exists to support this objective. ## Core Philosophy A Plot Line represents: > A question, conflict, objective, mystery, relationship, or narrative promise that the reader expects to see progress and eventually receive a payoff. If a reader would reasonably expect an answer or outcome, a Plot Line should exist. ## Plot Line Types Replace "Main Plot" with Plot Importance: ### Primary Major narrative threads driving the story. There may be multiple Primary Plot Lines. ### Secondary Supporting narrative threads. ### Minor Short-term or supporting arcs. ## Plot Line Properties ### Required Fields - Plot Line Name - Importance (Primary / Secondary / Minor) - Scope (Book / Series / Project) - Colour - Description ### Optional Fields - Emerges From Plot Line - Visible on Timeline ## Plot Events Plot events drive all structural changes. ### Event Types - Start - Progress - Reveal - Twist - Branch - Split - Merge - Resolve - Abandon ### Branch A new plot line emerges while the original continues. Source continues. Target begins. ### Split An existing plot line ends and becomes two or more independent threads. Source terminates. Targets begin. ### Merge Two or more plot lines combine into a single thread. Sources terminate. Target continues. ### Resolve The plot line concludes. Resolution without consequence should be questioned. ## Timeline Rendering - Scene columns remain the foundation. - All plot events align to the centre of their scene. - Use SVG overlays rather than CSS borders. - Draw: - Horizontal paths - Curved merge connectors - Curved branch connectors - Split connectors - Event nodes ## Plot Event Symbols - Progress: ● - Reveal: ★ - Twist: ◆ - Branch: ╲ - Split: ╱╲ - Merge: ◎ - Resolve: ◉ - Abandon: ✕ ## Plot Line States ### Active - Solid line - Full colour ### Neglected Criteria: - No progress for configurable number of scenes (default 10) Display: - Dashed line - Slight fade - Warning indicator Purpose: - Highlight potentially forgotten threads. ### Resolved - Greyed out - Reduced emphasis ### Resolved Without Consequence Allowed for: - Red herrings - Minor thematic threads Display: - Yellow tint - Question indicator Purpose: - Encourage authors to verify the thread genuinely belongs. ### Abandoned - Red styling - Cross marker Purpose: - Highlight potentially unsatisfactory narrative outcomes. ## Story Health Analytics ### Forgotten Plot Thread Criteria: - Active plot line - No events for X scenes Warning: "Potentially forgotten plot thread." ### Dangling Plot Thread Criteria: - Unresolved at manuscript end Warning: "Plot thread remains unresolved." ### Questionable Resolution Criteria: - Resolved without merge - Resolved without obvious consequence Warning: "Verify this thread provides sufficient payoff." ### Abandoned Plot Thread Criteria: - Explicitly abandoned Warning: "This plot line may disappoint readers." ### Dominant Plot Thread Criteria: - Appears in unusually high percentage of scenes Purpose: - Identify de facto primary plot lines. ## Guiding Principle PlotDirector should help authors answer: - What promises have I made? - Have I progressed them? - Have I forgotten them? - Have I delivered a satisfying payoff? The visual timeline should make these answers immediately obvious.