It is one of the most ordinary failures in a long series, and one of the most expensive. Not a plot hole. Not a magic system that breaks its own rules. Just a sister. In Book 2 she is introduced for half a page, named, given a glance of gray eyes, and folded back into the background. Three years and two more books later, she returns in Book 5 for a single line of dialogue, and she has a different name and different eyes.
Here are the two passages, side by side. The names below are illustrative, but the shape of the error is one that turns up again and again in long series.
What actually drifted
Why it happens: the math of attention
This isn't carelessness. It's arithmetic. A finished five-book series runs to hundreds of thousands of words, and no author holds all of them in working memory while drafting the next one. By the time the sister reappears in Book 5, the half-page that named her in Book 2 is buried under three years of drafting, cutting, and re-reading. The detail hasn't been forgotten so much as it has slipped out of active recall.
So the brain reconstructs. You need a sister in this scene, and your mind hands you one (warm, familiar, exactly the right emotional shape) and confidently fills in a name and a face. The name feels right because it is right, in the sense that it fits the rhythm and the world. It simply isn't the name you used the first time. The eye color works the same way: you "remember" it vividly, and the memory is a fresh invention.
This is why the error survives revision. When you reread Book 5, "Hannah" with brown eyes is internally consistent, emotionally true, and grammatically clean. Nothing on the page flags it, because nothing on that page is wrong. The conflict only exists across two books, and rereading is something we do one book at a time. An editor can be excellent and still miss it, because nobody reads Book 2 and Book 5 in the same sitting. The slip doesn't beat anyone's skill. It exploits the one thing skill can't fix: a memory that spans years of pages.
How a reader catches it (and why that's the worst case)
Your most devoted readers are the ones who will catch it, because they're the ones who reread. The fan who finishes Book 5 the day it drops, then goes back to reread the whole series from page one before the finale, holds both passages in active memory at once. A binge re-read does in a weekend what no single-book edit can.
And the reader who catches it rarely keeps it private. It goes in the review.
The "what else" question is where a single name slip stops costing one star and starts costing trust in the whole world. If the sister's name can change, can the timeline be trusted? The magic rules? The promise the series made in Book 1? When the slip fails publicly, in a review the next reader reads before buying, it stops being a craft note and becomes a sales problem.
StoryHelm reads one book at a time and records what each read finds: the characters, places, factions, and items, with details such as a character's physical description. The Series Atlas lists every book's entries together on its Shared canon page.
Across books, the cross-book check treats two characters as the same person only when their names match or are spelled almost alike, as Helen and Helena would be. It does not use aliases to connect books. Helen and Hannah are too far apart, so the Book 5 sister is filed as a new character. Inside each book nothing is wrong, so the Coherence Guardian, which reads one book at a time, has nothing to flag either. For this pair, that means:
- Name: not flagged. StoryHelm does not report a name that changes to a different name, in one book or across books.
- Eye color: not compared. Because Helen and Hannah never pair up, "gray" (Bk 2) is never set against "brown" (Bk 5).
What it gives you is the view to catch it yourself: both sisters sit on the Shared canon page, and opening each shows the facts her book recorded. Once both books call her by one name and have been read again, the next cross-book check you start pairs them and can flag the eye color, naming both books and showing what each records rather than quoting the passages. StoryHelm doesn't decide which is correct; you do. The goal is a choice made on purpose, before a reader makes it for you in a review.
The fix is a decision, not a correction
Once you have both sisters in view, the work is fast, and it's authorial, not mechanical:
- Find both sisters. The Shared canon page lists every book's characters together, so Helen and Hannah turn up on one page. Open each in her own book's Story Bible to see what that book records and up to three sentences that name her. A duplicate scan may list the two as a possible pair, but it is not built for a name change, so look for yourself.
- Decide the canon. Is she Helen or Hannah? Gray or brown? Maybe Book 5 is right and you've grown to prefer it. Either way, the call is yours.
- Fix it, then compare the books. Change the lines yourself; StoryHelm never edits your manuscript. Read the book you changed again so its Canon records her under the right name. The cross-book check runs only when you start one from your series' Checks page and confirm its credit cost, not when a read finishes or a book is added. Once both books call her by one name, it compares the appearance each records, so a leftover eye-color slip can surface. A second name change still won't.
- Or make it intentional. Sometimes a name change is the story: she remarried, went into hiding, was always lying. If so, keep it, and let the text say so. StoryHelm raised no flag here to mark; when a cross-book finding is on purpose, you can mark it intentional and add a note saying why.
That fourth option is the point worth lingering on. StoryHelm's job is not to enforce sameness. It's to surface the differences it can compare and leave the names to you, so every difference between Book 2 and Book 5 is one you chose, not one that slipped past you.