Editorial process
How the stories on this site are made, including the part most sites leave out.
The short version
The serials here are drafted by AI. The plan each story follows, the facts it is not allowed to break, and the standard every chapter is measured against are set by the people who run The Nightstand. Each draft then has to clear a sequence of checks, and a draft that fails a serious one is not published — it is sent back and written again.
No editor reads every chapter before it goes up. We would rather say that plainly than claim a review that does not happen. Most drafts are sent back before they reach anyone, and the rest of this page is the machinery that decides which ones.
1. The story bible comes first
Before any prose exists, a serial gets a bible. It fixes the cast — ages, occupations, what each person wants, and crucially what each person knows and when they learned it — along with the setting, the rules the story may not break, and a chapter-by-chapter calendar for the whole season.
The bible also carries the limits a draft is held to: how long a chapter may run, and how much of it has to be dialogue. A serial may tighten those limits but never loosen them, so the system that writes a story cannot quietly lower the bar it is judged against.
The season plan is itself reviewed before a word of prose is written: whether the story escalates, whether the secret is planted before it pays off, whether each chapter ends somewhere that makes the next one worth opening, and whether the ending is actually an ending.
2. Each chapter is planned before it is written
Every chapter has a beat — what happens, who is present, what changes, and which facts the chapter has to respect. Beats are written against the season calendar, so a chapter fills in a plan rather than drifting wherever the previous sentence happened to point.
3. The draft
A chapter is written from its beat, from the bible, and from a record of what the previous chapter established. Where a draft has been rejected before, the writer is told what was wrong with the last attempt, in the reviewer's own words.
4. Two kinds of checking, and a draft must clear both
The first kind is mechanical, and covers what a machine can be trusted to measure exactly: length against the serial's own range, how much of the chapter is dialogue, sentence rhythm, phrases that read as machine-written, and a comparison against every other chapter on this site to catch repeated passages. These are not judgement calls, so they are enforced literally.
The second kind is a reading. A different model reads the whole chapter against the bible and against our published rulebook, and reports what it finds sorted by severity: contradictions of established fact, plot and structure faults, and matters of style.
One rule decides which model does that reading, and it is the rule the whole process rests on: a chapter is never judged by a model that could have written it. A reviewer marking its own work is not quality control at all. The reviewer runs on a different provider from the writer, and the same principle governs every other reviewing step below.
5. The gate
A chapter is published only on a clean pass — no contradictions, no plot faults, and at most a couple of minor style notes. Anything beyond that is parked and rewritten.
Three things make that gate hard to talk past:
- The verdict is computed from what the review actually found, never from the label the model puts on its own report. A review that says "pass" while listing a serious fault publishes nothing.
- A review that comes back incomplete or unreadable counts as no review at all, and the chapter waits rather than going out unchecked.
- Every quotation a reviewer gives as evidence is checked against the chapter. A complaint quoting words that are not there is discarded.
Most drafts do not clear this on the first attempt. That is the system working, not a fault in it.
6. When a chapter and the bible disagree
Usually the chapter is wrong. Sometimes the bible is — a date that cannot be true, an age that does not survive arithmetic. So a disagreement goes to a third model, on a third provider, which decides which side is at fault.
If the plan was sound, the chapter is rewritten and the plan is left alone. If the bible was wrong, it is corrected — but only one named sentence at a time, and only after the system has proved that sentence exists exactly once in the field being changed. Nothing here is ever handed a whole document to rewrite, because then nobody can tell what moved.
7. Before a new serial reaches the site
A finished chapter can be technically spotless and still be dull, and no rulebook catches that. So before a new serial is published at all, a stand-in reader reads it and answers one question: would you open the next chapter?
If the answer is no, the serial does not go up. This has happened, and serials have sat unpublished because of it.
8. After publication
Publication is not the end of the checking.
- Every published chapter is read again and recorded with a verdict on whether a reader would carry on. It is a signal we watch, not a gate.
- Every chapter carries a continuity journal — what changed, who learned what, what a later chapter must respect. Those journals feed the next chapter, which is how the story keeps its own facts straight.
- Once a week the story bibles are audited for contradictions across entries, by three independent passes that have to agree before a finding counts.
What the people here actually do
They decide what the rules are: the rulebook every chapter is measured against, the phrases that are not allowed, the limits on length and dialogue, the fixed list of genres a story may be filed under. None of those can be changed by the system that writes the stories.
They set how hard it tries, how many chapters a serial needs before it can launch, and how much is spent. They read the reports the pipeline sends out every day. When something goes wrong — a plan that contradicts itself, a fact that leaked from the outline into the prose, a stretch where the drafting quietly stopped — they go in and fix it by hand.
Corrections
Published chapters can be changed, and are. Typos and continuity errors are fixed in place. Where a correction changes what happens in the story rather than how it reads, we say so on the chapter.
If you find something wrong, tell us: see contact. A chapter number and a sentence is enough. Continuity reports are genuinely useful and we act on them.
What we do not do
We do not claim these stories are written by hand. We do not claim they are written entirely by a machine with nobody deciding anything, either — the plan, the rules, and the standard are ours, and the machinery above exists because volume without a gate is worthless.
We do not publish a draft that fails the checks, and we do not edit a draft sentence by sentence until a complaint goes away. A chapter that cannot pass gets rewritten from its plan.
Why this page exists
Readers are entitled to know how what they are reading was made. A site that uses AI and says nothing is asking to be found out; a site that uses AI and overstates the human involvement is worse, because the claim collapses the first time anyone checks it.
So this page describes the process we actually run — including the part where no person reads every chapter — and the checks that stand in its place.