Writing
Keeping a character consistent 500 chapters later
Here is a small problem that turns out to be a large one. A character is introduced in chapter three. Four hundred and seventy-seven chapters later, the story refers back to something about them, and the translation has to get it right, in the correct form, without having read chapter three since it was written.
Web serials run long. Hundreds of chapters, sometimes more than a thousand, released over years. A fact laid down early has to keep holding late, and translating that late chapter correctly depends on knowing the fact. This sounds like a memory problem, and it is, but not the kind of memory people usually reach for.
Why the obvious answers do not work
The first instinct is to show the model everything. Give it the whole serial as context and let it keep the facts straight itself. This does not work, and it does not work for a structural reason rather than a temporary one: a whole serial does not fit. There is no context window large enough to hold a thousand chapters, and there is unlikely to be one soon enough to matter. You cannot solve consistency by showing the model the entire book, because you cannot show the model the entire book.
The second instinct is to retrieve. Do not show the whole serial, just fetch the passages relevant to the chapter you are translating and include those. This is closer, but it retrieves the wrong kind of thing. Fetching passages that are similar to the current chapter gives you prose that resembles the current chapter. What you actually need is the facts themselves, in their correct form: this character’s name, this title, this allegiance. A pile of similar-sounding paragraphs is not that. It is more text to read, not an answer to the question “what is true here.”
The third instinct is the one that breaks most quietly, so it is worth stating carefully.
Facts change, and when matters
Facts in a story are not fixed. They change on purpose. A character gains a title. Someone switches sides. A person dies. A secret that was true and hidden in chapter ten becomes public in chapter three hundred. The story is, in large part, the record of these changes. Which means the truth of any fact depends on when in the story you are asking.
This is what makes long-serial consistency genuinely hard, and it is where naive memory fails worst. Translating chapter two hundred has to use what was true as of chapter two hundred. Not a stale fact from chapter ten that has since been overtaken by events. And, just as importantly, not a fact from chapter four hundred and fifty that has not happened yet. Reaching forward is not a harmless error. If the memory system hands the translator a fact that the reader of chapter two hundred is not supposed to know, the translation leaks a spoiler into a chapter that was carefully keeping the secret. Consistency and spoiler-safety turn out to be the same problem seen from two sides: both require knowing not just what is true, but what was true then.
A memory that only stores the latest version of every fact cannot do this. It will confidently tell you the character’s final title while you are translating the chapter where they had not earned it yet. Correct fact, wrong time. In a serial, wrong time is just wrong.
What the problem actually demands
Put the three difficulties together and they point at one thing. Scale rules out holding the whole book in view. The nature of the need rules out retrieving similar text instead of facts. And the fact that facts change over time rules out any memory that keeps only a single, current value.
What is left is a specific shape of solution: an explicit, queryable model of the story’s world that tracks how each fact changes over time. Not a pile of retrieved passages, but a memory of state, able to answer “as of chapter two hundred, this is what is true” and to answer it differently for chapter twenty and chapter five hundred. The translator does not read the story to remember it. It asks the world model a precise question and gets the version of the fact that was true at that exact point, no earlier and no later.
That is also, and not by coincidence, what keeps a translation spoiler-safe. A memory that knows when a fact became true is a memory that knows which facts a given chapter is allowed to reveal. Coherence across five hundred chapters and never spoiling the reader are the same guarantee, and they come from the same place: treating the story’s world as something that has a history, not just a present.
This is the part of the system that lets long serials stay themselves across languages. In Tellura, a five-hundred-chapter novel can be read in translation and still hold together, because a fact set down in chapter three is still there in chapter four hundred and eighty, in the form it had back then, waiting to be asked for.