StoryBook

📖 Storybook — The story remembers. A lightweight living-memory system for long-form interactive stories. Storybook preserves recent events as Scene Logs, binds older history into searchable Chronicles, tracks unresolved story threads, and gives important characters their own personal memories—without rewriting your entire campaign state every turn. Current Status - Beta✨ Full Package Description 📖✨ Storybook ✨📖 The story remembers. Stories rarely fall apart because nothing interesting happened. They fall apart because the AI forgets what happened. A promise made twenty scenes ago disappears. An NPC stops remembering a betrayal. A mystery is introduced and quietly abandoned. A character recognizes someone they have never met—or fails to recognize someone who changed their life. Important events leave the active context window, and the campaign slowly loses its own history. Storybook is a lightweight living-memory system designed to prevent that. It gives long-form interactive stories a structured memory outside the temporary conversation window, preserving the details that future scenes may depend on without turning every response into a complicated database update. Install Storybook into a new or existing project and its memory structure is ready to use. No setup wizard, genre selection, or campaign conversion process is required. 🌙 Memory Without Constant Maintenance Storybook is designed to stay quiet during ordinary play. It does not attempt to summarize the campaign after every response. It does not rewrite dozens of files each turn. It does not create a permanent record of every sentence spoken. Instead, Storybook allows the story to unfold naturally while holding the most recent stretch of play inside a permanent Current Scene. After eight completed GM responses, that memory segment is preserved as an archived Scene Log. The Current Scene is then cleared and reused for the next segment. The fictional scene itself does not need to end. A battle, journey, negotiation, investigation, or emotional conversation can continue naturally across several memory segments. Storybook creates archival boundaries for continuity—it does not force artificial stopping points into the narrative. ✨ Scene Logs Each completed memory segment becomes a Scene Log: a compact objective record of what happened and what changed. A Scene Log can preserve: - The central events of the segment - Where and approximately when it occurred - The characters who were physically present - The kind of scene that took place - Important discoveries, decisions, conflicts, and consequences - Searchable tags connected to the people, places, and subjects involved Scene Logs are intentionally concise. Their purpose is not to reproduce the original conversation word for word, but to preserve the facts and developments that the story may need later. This gives the GM a reliable record when an older detail becomes relevant again. 🌌 The Story Ledger At the center of Storybook is the Story Ledger. The Story Ledger holds the compressed state of the campaign: the information needed to understand where the story currently stands without loading its entire history. It tracks things such as: - The current in-game date and approximate time - A concise summary of the active situation - The current memory segment - Major developments that became permanently true - Unresolved narrative threads - Recently archived scenes - The number of memory segments and Chronicles created - Older history waiting to be bound - The campaign’s Recall Constellation The Story Ledger is not a transcript. It is the story’s living table of contents—the place where the GM can quickly see what matters now and where older information can be found. ✧ The Recall Constellation Every important archived memory receives a small set of searchable tags. A tag might represent: - A named character - A location - A faction - A relationship - A mystery - A conflict - An important object - A revelation - A promise - A recurring subject Together, these tags form the Recall Constellation. Each tag acts like a star connected to the memories where it appeared. Recent occurrences lead directly to their Scene Logs, while older occurrences lead into the Chronicles that preserve them. This gives the GM a guided way to recover information. Instead of searching the entire project for a name or vaguely guessing what happened, the GM can follow a clear path: Tag → relevant Scene or Chronicle → exact archived memory The Recall Constellation allows Storybook to remain compact without making older history difficult to reach. 📚 Chronicles As Scene Logs accumulate, Storybook binds them into Chronicles. A Chronicle is a chapter of campaign history containing a group of archived memory segments, their shared summary, and a local constellation of the important people, places, conflicts, and revelations within them. Chronicles keep old history organized without crowding the active Story Ledger. Recent events remain close to the surface. Older events become chapters. The story can continue growing without forcing the GM to carry every past event in active context. Each Chronicle provides direct access to the Scene Logs preserved within it, allowing the GM to move from a broad chapter summary to the exact memory where something occurred. 💫 Living Memories Objective history is only one kind of memory. Characters do not always know the full truth. They remember events from their own perspective. They can misunderstand what happened, believe a lie, keep a secret, forget a detail, or hold onto an emotional impression long after the exact words have faded. Storybook can create a Living Memory for important characters who need persistent personal continuity. A Living Memory may preserve: - The character’s current emotional state - Their important relationships - Their personal history with the player - Promises, favors, betrayals, and debts - Important memories - Private knowledge - Secrets and hidden identities - Incorrect beliefs or misunderstandings - Memories lost through genuine in-world causes This distinction is important: The Story Ledger records what objectively happened. A Living Memory records what a particular character believes happened. Because these memories remain separate, characters can disagree with the official history without the system treating that disagreement as an error. Storybook creates and updates Living Memories selectively. Background characters do not need permanent psychological files, and important characters are updated only when something meaningful changes. 🕯️ Unfinished Threads Long stories contain questions that should not be forgotten simply because they have not been answered yet. Storybook tracks unresolved narrative threads such as: - A mystery that remains unsolved - A warning that has not yet come true - An enemy whose plan is still developing - A promise waiting to be fulfilled - A consequence that has not arrived - A secret the player has not uncovered - A relationship left in an unstable state When a thread is resolved, its conclusion becomes part of the permanent story history. This helps the campaign remember not only what has happened, but also what is still waiting to happen. 🛡️ Built for Reliable Long-Term Continuity Memory systems can create new problems when they are too aggressive or poorly organized. Storybook includes safeguards designed to keep its records stable. It protects against issues such as: - Empty memory segments being archived - Duplicate Scene Logs - Scene IDs changing unexpectedly - Chronicles covering the same scenes twice - Partial archival attempts corrupting campaign counters - Blank templates being mistaken for real story records - A failed character-memory update blocking objective history - The permanent Current Scene being deleted or replaced - Current Scene artwork disappearing during a reset - Old memories being overwritten by uncertain AI recollection Stored records remain the source of truth. When the AI is uncertain, it is expected to retrieve the relevant memory rather than invent a replacement. 🌠 Made for Any Kind of Story Storybook is genre-neutral. It can support fantasy adventures, superhero campaigns, science-fiction epics, romances, mysteries, horror stories, political dramas, academy settings, survival campaigns, reincarnation stories, established fictional universes, and entirely original worlds. It does not dictate your setting, mechanics, tone, or writing style. Storybook can be used as a standalone continuity system or alongside a larger worldbuilding framework such as the Living World Engine. When combining it with another package, only one system should be responsible for automatically archiving campaign scenes. 📖 What Storybook Is For Storybook helps an interactive story answer the questions that become more important the longer it runs: What happened? What permanently changed? Who was actually there? What remains unresolved? What does this character remember? What does this character only believe? Where can an older event be found? What must carry forward into the next scene? Storybook does not try to remember everything. It remembers what the story cannot afford to lose. 📖 Storybook The story remembers.