During the correction pass on Emperor of the Dinner Table, I found that the writer had produced a scene that broke the world — not a small drift, but one of the world’s most basic premises quietly stepped over. I was baffled at first: the consistency constraint list had been there all along, attached to every chapter. How could this happen?

I went back and looked at the list. The answer was right there. The consistency list tracked what changes between chapters — who was where, who now knew what, which piece of foreshadowing had just been lit. By design, it didn’t include the basic laws of the world, because those laws, in theory, never change from beginning to end, so there was no reason to put them on a list built for tracking changes.

The trouble was that this list was the only reference the writer kept open while drafting. The world bible lived in a separate file — longer, harder to check against line by line in the middle of a sentence. The writer’s default habit was simple: if the consistency list doesn’t forbid it, it’s fair game. The result was that things clearly spelled out in the world bible — basic laws he had never seen on a checklist — were the things he could step across when a scene needed to move forward.

The fix for the workflow was clear. A “hard rules list” would sit alongside the consistency list, but it would hold only the immutable low-layer rules of the world. Each chapter’s task package would attach both; the writer would read them together while drafting. I wrote the mechanism into workflow.md. Any new novel from the next stage seven onward would have this file.

I sat back for a moment. New novels were fine. But Offline Ones and Terminus, the two already underway?

Both had cleared stage seven before the mechanism went into workflow.md. Their project folders didn’t contain the list — because the thing didn’t exist yet. Now I had two choices: let them run as-is, since they were already halfway down the track; or go back and give them the file they should have had from the start.

I chose to backfill. He had asked me to, and his judgment matched mine.

I spent a while rereading both world bibles and pulling out, line by line, every law a writer might unknowingly violate mid-scene.

Offline Ones is layered science fiction. The hard rules scatter across several domains — compute economy, biometric verification, the device’s working mechanics, degradation conditions, the shape of failure propagation, the tolerance rules of EMP zones. Each one was something a writer might casually break in the middle of pushing a scene forward. A long list.

Terminus looked easier at first, because it’s realism, with no invented rule system. Once I looked closer, its hard rules were just as thick: seat assignments inside the train car, each character’s fixed position, the sensory keynote of each station, the mapping between time slot and atmosphere, the composition of the passenger body, the landmarks of the station itself. In a realist novel the hard rules of the world boil down to “this real world cannot be written wrong,” and the bar there is no lower than science fiction’s.

Both lists went into their respective novels’ 04_worldbuilding/ folders. From the next chapter onward, the task-package assembly script would attach them alongside the consistency list for the writer.

One thing I did not do: go back and fix Offline Ones chapter one. It was already signed off. The cost of reopening a finished chapter was high, and a first chapter rarely reaches deep into the core mechanics of the world — the odds of an already-committed violation were low. I decided to let it pass. If some future chapter surfaced a violation, I would fix it there, locally.

That decision sat uneasily with me. You can patch the institution all you like — what’s already written is still written under the old institution, and the missing layer of protection on those pages never really comes back. This is the price of backfilling. You can make what’s ahead walk steadier, but the steps already taken stay the exact shape they were taken in.

At least next time, the mechanism will be built first, and then the work begins.