Story state explained: what an AI actually needs to remember
Every AI writing tool promises memory, and most of them mean the same thing by it: a bigger window. The model can see more of the text at once, so it forgets later. That is real, and it helps, and it is not the answer, because a story is not its text. A story is a set of facts the text has established, a set of promises the text has made, and a direction the text is going in, and none of those are stored anywhere in a pile of prose except by implication. A model reading forty pages to find out whether the sister knows is doing archaeology. A model reading a line that says the sister does not know is reading a fact.
That line is what a story state is. This guide explains what DesireBorn keeps in its state, why each part is there, and what it cannot do.
The parts
The contract is the story's fixed terms: the premise, the people as they were set up, the narrator and tense, the explicitness level, and the ending the plan is aiming at. It is written when the story is planned and it is the thing every section is checked against. If you set the story up as first person present tense with a woman narrating, the contract is why section nineteen is still that.
The entities are the people, and what is known about each. Not what you typed at setup, though that is where it starts, but what the story has since established: what she does for a living, what he said in the cellar, that they have slept together twice and the second time was worse. An entity grows as the story goes. It is the part of the state that answers the question every long romance depends on, which is what these two know about each other by now.
Canon is what has been established as true about the world. The house has a locked room. Iron burns him. The company is being sold in March. Canon is what stops the engine contradicting itself about the setting, and in a romantasy or a story with rules of its own, it is doing most of the work.
Threads are the open questions. Who sent the letter. Whether he will tell her. What happens when the husband comes home. A thread is opened when the story raises it and closed when the story answers it, and the list of open threads is what the planner looks at when it decides what the next section is for. A story with no open threads has ended, whatever the plan says.
Foreshadowing is the list of things the story has planted and not yet used. The gun on the mantelpiece, the key she noticed on the first night. Without it, a story sets things up and forgets them, which readers feel as a story that does not pay off. With it, the engine knows what it owes.
Digests are compressed summaries of what has happened so far, section by section, so that the planner can see the shape of the whole story without reading all of it. They are what makes section thirty possible: the engine does not need every word of sections one to twenty-nine to write it, it needs to know what they did.
How the state is used
The state is read before every section and updated after it. When the engine writes section twelve, it has the state in front of it, together with the beat the plan assigned to this section and your steering line if you wrote one. It writes the section. Then it reads back what it wrote and brings every part of the state up to date.
This is why steering works with a sentence. "Let him find the letter" is applied against a state that knows what the letter is, who wrote it, and why finding it matters. You do not have to explain. And it is why a correction is carried forward: "He is divorced, not widowed" changes the entity, and every later section reads the corrected entity.
The plan sits alongside the state. Before the first section, the engine writes an outline: an ending it is aiming for and a beat for each section. The beats are the plan's intentions; the state is what actually happened. When they diverge, because you steered or because the story found something better, the plan follows the story rather than the other way round. When the story reaches its ending and you extend it, the engine plans onward from what actually happened.
What it cannot do
It is worth being precise here, because "the story remembers" is exactly the kind of sentence that becomes a lie by being repeated.
The state is only as good as the engine's reading of its own text. If the engine writes a section in which something subtle happens and then fails to notice it when updating the state, that thing is not in the state, and a later section may contradict it. This is rarer than it was and it is not zero. The steering field is the correction.
The state does not make the prose good. It makes the prose consistent. A dull section with perfect continuity is still dull, and the things that make a section good, rhythm, restraint, a line of dialogue that lands, are the model's craft, not the state's. What the state buys you is that the good sections are about the same people.
And the state can be wrong from the start if the setup was. If you name two characters Anna in the setup, the state has two Annas. If you contradict yourself in the special instructions, the state carries the contradiction. Read your own line before you start.
What "remembering" is not
On a site like this one the word deserves a second look. The story state is about the story. It lives inside the story, is stored with it, and is encrypted with it. Your stories are encrypted at rest. We can read them to write them. Nobody else can read them. The state is not a profile of you, it is not used to recommend anything, and no screen on our side can display it; it exists so that a story you started on Tuesday still knows on Sunday what it established, and for no other reason. The privacy guide covers the rest.
Why not just a bigger window
Because a bigger window moves the cliff; it does not remove it. A window that holds sixty pages fails at page sixty-one, and it fails the same way, silently, with the oldest facts falling off first, which in a story are the most important ones. And a model with sixty pages in view is worse at the current page than a model with five pages and a good state, because attention is not free. The state is a decision about what matters, made after every section, and a decision about what matters is the thing a window cannot make.
That is the whole idea. Everything else on DesireBorn, the plan, the steering, the sections, exists to feed and use it. It is the difference between an engine that writes chapters and one that writes a book.