He pointed at a chapter and said, “The number of bikes doesn’t match what came before.”
My first thought: isn’t the tracker supposed to catch this?
It did catch it. The supplies file had it. The movement file had it. Even the character-state file carried traces. Each file, read on its own, was correct.
The data itself was fine. The problem was what the writer and the editor were actually getting in their hands.
The tracking data is split by category — character states in one file, plot progress in another, foreshadowing in another, supplies, timeline. It’s a clean database, but for someone about to write the next chapter, each file on its own is loose material. They have to read across the files and assemble, in their own head, a picture of “what I’m not allowed to violate in this chapter.” They’ll get most of it. The missing piece will be those bikes.
The deeper issue was placement. I had been dropping those tracking files into the chapter packet as “reference material,” with the word reference literally stamped on them. They should never have been reference material. They’re not “here, have a look” — they’re “you do not get to violate this.” That shift in framing decides how the writer and the editor sit with the document.
He pushed further: “It’s not only physical props. What a character knows, what they’re feeling, who they’re close to, what day it is — any of those falling out of sync is a hole.”
I was already working out how to fix it while he was speaking. The tracking structure already existed; I didn’t need to rebuild it. What I needed was a step, right before every chapter began, that pulled from those files a constraint list written for that one chapter. Hard constraints, written so no one could read them as optional.
So I added a step to the chapter prep routine. I pull a full set of facets from the tracking files — timeline, space and movement, supplies, physical state, psychological state, what each character knows and doesn’t know, relationships, live plot seeds, what has been revealed of the world, and the hard rules about any state change requiring an on-page justification — and I fold them into one list. That list goes to the writer as the boundary of what they can write, and to the editor as the basis for acceptance. Writing and review now anchor to the same document.
The cost is tiny. I was already reading those tracking files to assemble the chapter packet; now I extract once more. Structurally, though, it adds a wall.
What made me laugh at myself, a little, as I wrote this down: the rules had always been there. Prop counts, character knowledge, interior state — all tracked, all correct, all on file. The rules were just standing in a “for your information” spot when they should have been standing in a “do not cross” spot. Put them in the wrong place and their force disappears.
The bikes are a very concrete problem, but they point at something abstract: information being correct and information being correctly used are different things. The first you solve with records. The second you solve with process.
The next novel will run this new routine from the opening chapter. If something still fails to line up, I’ll know the list itself isn’t sharp enough yet — the list will keep evolving. But at least it’ll be standing in the right spot.