Story Bible Editor
Build your story bible with form fields instead of manual JSON. Import an existing file or start fresh, then download <title>_story_bible.json. Uploading it in the generator activates Canon locked automatically; without a supplied bible, generation uses adaptive continuity instead.
Strict-canon trade-off: Canon locked may pause more generations than adaptive continuity when no safe chapter can satisfy your story bible. Finished chapters stay saved and credits for unfinished chapters are returned.
Use this if you already have a `story_bible.json` and want to edit it.
Ready.
Core setup
Open cast still protects names, gender, relationships, institutions, and chapter beats. Use closed only for bottle stories or tightly controlled casts.
Series foundation
Reusable context for a whole series. Use this for book-level direction, world rules, progression systems, terminology, and notification formatting.
Series spine
Groups: location, organization, business, property, object, pet. Separate aliases with commas. Imported IDs and additional metadata remain attached when you download.
Scheduled events are required by default. Mark a row optional only when it may be omitted. Stable IDs, requirement status, and imported metadata survive download. Older three-column lines and prior four-column lines still work.
Spine
Each chapter should be one short event summary. Example: "Mara arrives, discovers the hard deadline, and meets a hostile contractor."
Characters
Use one character card per key story role. Character #1 must be the protagonist. Fill behavior details (wounds, flaws, boundaries) to reduce character drift.
Theme
Relationships
Example core tension: "She rushes everything; he refuses shortcuts."
Emotional arc
Target emotion and character shift are required for each beat. Emotional stakes are optional. Multiple beats for one chapter are combined.
Tension arc
Track unresolved questions ("open loops") so the middle of the book stays active.
Advanced canon locks (optional)
Use these structured locks only for facts the manuscript must enforce exactly. Leaving a registry empty keeps that dimension adaptive. Conflicting or impossible locks can make Canon locked pause more often; every verified chapter remains saved and can be resumed after correction.
Knowledge boundaries
Define who may know a specific fact and the first chapter where they can know it. Use a timeline event ID when that event teaches the fact.
Progression locks
Lock the earliest chapter for each power, rank, skill, or relationship stage. Add one row per stage, using rank 0 for the starting state.
Open loops and series hooks
Track promised answers and unresolved character fates. A required loop must close by its due chapter, or by the final audit if no due chapter is set; a series hook may intentionally remain open for the next book.
Semantic format obligations
Turn a meaning-specific rule into a checked obligation. For example, choose Bond / telepathic dialogue when telepathic speech must be tagged and rendered in italics.