Five Books In. Still Straight.
Multi-book continuity across half a million words is a memory problem dressed up as a writing problem. Ishvana is the one keeping track of which character died in book two, which faction the Duke's bastard half-sister swore loyalty to, and which moon phase it is on the day of the assassination. So you can spend the attention on the prose.
Series Writing Breaks Every Writing Tool
Book three establishes that the Duke died at the Battle of Harrow. Book five, he shows up at his daughter's wedding and nobody catches it. Your editor reads it. Your beta readers read it. You read it yourself. Three years of drafting later, a reader on Goodreads finds it in chapter eight of book five and your reviews are about how you can't keep your own story straight.
- Your Series Bible Is a Liability
- It started as a 40-page Google Doc in 2021. It's now 180 pages, mostly out of date, and nobody has touched it since book three launched. You don't trust it anymore, so you stopped updating it.
- Tools Don't Know About Each Other
- Your characters live in Notion. Your timeline is a Miro board. Your map is in Inkarnate. Your manuscript is in Scrivener. None of these tools can read your prose or fact-check against your bible.
- Continuity Errors Compound
- Every book adds new facts. Every new fact is a chance to contradict an old one. By book five the cognitive load of remembering everything is impossible, and no editor has the budget to reread the whole series.
- Character Knowledge Leaks
- Your assassin reveals something in book four that she doesn't learn until book six. Your mentor references a prophecy in chapter two that isn't told to her until chapter nine. These mistakes are invisible until a reader catches them.
The Hierarchy a Series Actually Needs
Seven levels deep: Series → Book → Part → Act → Chapter → Scene → Beat. Your Legendry spans the whole series, your characters persist across books, and the timeline knows which events happened in which volume. Built for projects that span a decade, though, rather than projects that fit in a single file.
Custom fantasy calendars with your world's months, seasons, and eras. Swimlane views per character across every book.
Series-Scoped Legendry
Characters, locations, factions, and magic systems live at the series level. Every book reads from the same database, so update the Duke's eye color once and every book agrees with itself again.
Per-Book Outlines
Each book has its own seven-level outline inside the series. Drag scenes between books, restructure at any level, and keep the overarching arcs visible while you're in the weeds of a single volume.
Cross-Book Character Tracking
The Character Knowledge matrix spans the entire series across every book. Track what each character knows at the start of every volume, and the exact scenes that changed what they knew.
Custom Fantasy Calendars
Your world's months, weeks, days, seasons, and era names. Tag events with the book they happen in. Swimlane views per character across the whole series, so you can see who was where in any given year.
Lorekeeper Catches What You Can't
By book four your manuscript is a million words across four volumes and sixty chapters. You can't reread it before every writing session. Lorekeeper reads the whole corpus and runs actual ML anomaly detection on every save, which is what your brain wishes it could do around hour six.
- Entity-Level Consistency
- Catches name spelling drift (Aldric becomes Alric somewhere around chapter twelve), eye color changes, hometown variations across books.
- Rule-Level Consistency
- Flags magic system violations against the rules you established in earlier books. Your fireballs can't suddenly work underwater in book five.
- Knowledge-Level Consistency
- Catches characters revealing things they shouldn't know yet. Cross-references the Character Knowledge matrix for you, without you having to ask.
- Temporal Consistency
- Warns when events contradict your timeline. If Book Three puts the Duke at the capital in spring, Book Five can't put him in the south that same season.
- Dismissal Learning
- When you override a flag as a deliberate choice, Lorekeeper remembers and stops flagging it. Over time it learns the difference between your real mistakes and your real style choices.
ML-powered anomaly detection. Severity-coded results with full location references to the offending passages.
Who Knew What, and When
Information leaks are the most embarrassing continuity errors in multi-book fiction, though they're also the hardest to catch yourself. The Character Knowledge matrix lets you define what each character knows at each point in the story. When your prose references something a character shouldn't know yet, Ishvana flags it before a reader does.
Define what each character knows, when they learned it, and what they still don't have access to.
Use What You Need. Skip the Rest.
Not every series needs the Mechanics engine. Not every author wants a conlang. If you only need the editor, Legendry, and Lorekeeper, that's already a complete setup. The rest sits there quietly until the day you decide you need it.
One purchase covers every book in the series. Every revision. Every prequel or spinoff you decide to write five years from now. You're not paying per book, and you're not paying a subscription that scales with word count. You bought the software once, and the software is yours.
Questions From Series Authors
How big of a series can Ishvana handle?
The database is SQLite, which handles terabytes comfortably. In practice, the bottleneck is your machine's RAM when loading the editor with 500,000-word documents. A ten-book series with thousands of lore entries works fine on any modern system.
I'm four books into a series already. Can I import?
Yes. Import your existing manuscripts via DOCX or Markdown. Ishvana's entity extraction can read your prose and build an initial Legendry, pulling out every character, place, and faction. You then review, edit, and add detail. Most authors import their existing series in an afternoon.
Can I share my series bible with co-authors or editors?
Your Legendry exports to Markdown, JSON, and plain text. Share the exports with editors or beta readers as reference material. Ishvana itself is single-author (no real-time collaboration), but the data is in standard formats that anyone can read.
What if my series structure changes mid-draft?
The outline is designed for restructuring. Drag entire books between positions in the series. Merge two books into one. Split a planned standalone into a trilogy. The seven-level hierarchy flexes to match your actual structure.
Does Ishvana work for shared universes?
Yes, within a single author's workflow. If you have multiple series in the same universe, you can keep them as separate projects that reference the same Legendry, or as a single project with multiple series-level nodes. Whichever matches your mental model.
Is this only for fantasy and sci-fi series?
No. The tools are genre-agnostic. Mystery series with recurring detectives, crime sagas, historical fiction spanning generations, literary cycle novels. Any series that benefits from a consistent bible and continuity checking benefits from Ishvana.