# Novel II — Worldbuilding: Maps, Timelines, Glossaries
In ["Novel II — Worldbuilding: Consistency Engines"](/harrys-desk/novel-ii-worldbuilding-consistency-engines) I said a place that wants something on page twelve has to keep wanting it on page three hundred, or the want was a mood. I asked you for a five-line ledger and a scene that did not get easier. If you did that work, you have an engine. Today we give it instruments you can hold.
The claim is easy to mishear as a request for appendices. It is not. A map, a timeline, and a glossary are not the novel's extra credit. They are objects that refuse. A map that will not grow a river because the love scene would like water. A timeline that will not let two armies occupy the same week because the prompt compressed the march. A glossary that will not let a word mean its opposite because the scene is tender. The model will offer to generate all three overnight. That offer is a wiki in three files. Completeness is what wikis are for. Refusal is what a second witness needs.
By the end you should know which marks you make by hand, which drafts you may ask the model to attempt under constraint, and how to tell an instrument from a brochure with coordinates.
Instruments, Not Appendices
Readers meet maps and glossaries at the back of the book, so we treat them as courtesy. Tolkien's foldout. Herbert's terminology. The family tree no one consults until chapter thirty. Courtesy is a publishing decision. The working objects are earlier and meaner. They exist so that you, not the reader, can be told no.
A wiki is a completeness machine. I said so on Wednesday, and I am saying it again because the model loves the assignment "build me a world bible." It will give you a map with every village named, a timeline from the founding, and a glossary of two hundred terms, most of them flavor. Flavor is texture that has not been used. Unused texture is allowed to drift. A two-hundred-entry glossary is a completeness leak wearing a scholarly coat.
An instrument is small enough to check. Five named places and the days between them. A column of dates for events that have already happened on the page. Twelve words that cost something, and what they cost. If you cannot hold the object in a sitting, it will not veto a chapter. You will not open it. An unread map is wallpaper with a compass rose.
In ["Novel II — Worldbuilding: Setting as Character"](/harrys-desk/novel-ii-worldbuilding-setting-as-character) I asked you to keep Document W off the scene prompt. The same rule holds. Do not paste the map, the timeline, or the glossary into the generation. Put two or three constraints the scene actually touches. The mill is east of the well. The march takes eleven days. The word for the accident is not spoken. Then run the objects against what arrives. The objects are the pass, not the prompt.
*Always Coming Home* is a book that pretends to be the instruments. Le Guin can do that because the instruments were the art. You are not writing that book unless you are. You are writing a novel whose second witness needs a few vetoes. Steal the veto, not the apparatus.
The Map That Refuses a River
A map is spatial physics. Distance is a cost. Roads take time. A hill that eats sound on Monday still eats it if you drew the mill on the other side. The model does not have a map. It has a prior in which parties arrive when the scene is ready, inns appear at dusk, and water is near any conversation that would like to be near water.
This is the refill with coordinates. The drought you hired wants the well unused by strangers. The generated map grows a creek behind the kitchen because reunion scenes, in the corpus, happen near a window with a view. You did not decide on a creek. The prompt was thin and the prior is thick. A hand map, even an ugly one, will not grow that creek. That is the whole point of drawing it.
You do not need cartography. You need five places that have already acted on the page, and the cost of moving between them. The well. The mill. The house whose window faces the mill. The road that takes a day. The door no one uses, which is a location even if it is only a door. Write the days. Write what you cannot see from where. If the harbor is reachable without passing the mill, the mill was scenery. If you can get water without the well, the well was a mood.
Tolkien's walking times are slightly mad, and they are a physics decision: the Shire is not adjacent to Mordor because the chapter is impatient. Arrakis does not need a pretty map in the scene. It needs the stillsuit and the fact that open air is a conversation with a cost. Earthsea is water. If you generate a land-bridge because two characters need to meet by nightfall, you have written a different archipelago.
The AI accent of the map is convenience. Secret passes. Rivers that appear in the fold where the plot is thirsty. A town that is "a day's ride" from everywhere, which is how a model says it has not chosen a scale. Strike convenience on sight. If a new feature exists to make this chapter easier, it is a refill. Either it was already on the map, or you go back and cause it — a road that was always there, a spring someone dug in chapter two — or you strike it and keep the drought.
Do not ask the model to "generate a map of the region." You will get a brochure with coordinates: named districts, a majestic range, a river that explains the economy, three towns from the same naming function. Draw five marks yourself. If you cannot draw, list them in a column with distances. A list that refuses is a map. A generated image that agrees with the scene is not.
After the draft, open the map. Did a creek arrive. Did the walk shrink. Did the mill move. Mark the refill. The map's job is to make that marking obvious.
The Timeline That Refuses Two Armies
A timeline is political physics plus duration. Who paid, and when. Two armies cannot occupy the same week unless you caused the occupation. A child cannot be twelve in chapter three and sixteen in chapter four because the model needed a love scene and sixteen is the prior for love scenes. Harvest and the first snow cannot share a page because the prompt asked for abundance and then for dread.
The model has no duration. Each prompt is a new room. If the note on the door does not say that the march began on the third and cannot arrive before the fourteenth, the army arrives when the chapter wants a siege. Special cases expire when the prompt ends. I said this on Wednesday about wells. It is worse with time, because time in training data is a mood. Flashbacks are unmarked. Seasons are metaphorical. "Three years later" is a header the model will invent to be helpful.
You do not need a chronicle from the founding. You need the dates of events that have already been promoted — the reader has seen them — and the minimum durations your physics requires. The march takes eleven days. The well has been low since the accident. She has been back in the house for a week. He cannot have been in both kitchens. Write those as a column. After each chapter, add a line: what time did on the page, and whether anyone paid a political cost. That is Wednesday's ledger with a clock.
A caused change is still allowed. Someone sabotages the well; we watched it. The gallery rumor is withdrawn; the children feel the obedience slip. The timeline records the payment. What it refuses is the uncaused coincidence: the army that teleported, the winter that arrived because the marriage failed, the decade that vanished between chapters because the model was smoothing.
In ["Novel II — Deep Craft: Pacing and Tension"](/harrys-desk/novel-ii-deep-craft-pacing-and-tension) I said tension is the reader's desire to know. Duration is one of the ways they know. If the siege starts the morning after the departure, they stop trusting the second witness. Atmosphere will not get them back. They will not name the problem as "timeline." They will name it as the book going soft.
Do not generate "a complete timeline of the kingdom." Completeness will invent kings so the dates have somewhere to sit. Those kings will leak into a scene. A character will think, helpfully, about the succession. You have seen this leak. It is the encyclopedia smuggle with a calendar.
The Glossary That Refuses a Tender Word
A glossary, in the working sense, is not a courtesy list for readers who missed a definition. It is a list of words that cannot be used cheaply. In Earthsea, names cost. On Arrakis, stillsuit, sietch, spice — not flavor. Physics. If the stillsuit comes off because the scene is intimate, and open air was the cost of speech, you refunded the cost and called it character development. The word had a job. You fired it for the mood.
The model is fluent in the cheap word. It will let a term mean its opposite because the paragraph is tender, or comic, or explanatory. Magic that cost in chapter one is a metaphor by chapter nine. A title that was an insult becomes a nickname. The accident, which the town wants unspoken, is named in interiority because interiority, in the corpus, is where truth lives. You hired a politics of speech. A glossary that does not veto the naming has failed.
Twelve words. Not two hundred. For each: the word, what it costs, and whether it has been used on the page. If it has, it is promoted; it cannot quietly change. If you cannot fill the cost, the word is texture. Texture may drift until someone speaks it. Then it is physics.
Gene Wolfe can bury a world in archaic English because the words are the map. You are not Wolfe unless you are. You need the twelve that your Document W already implied. The word no one uses for the mine. The name of the whistle. What they call strangers at the well. If a generated scene uses a synonym to avoid the cost — "the evening bell" for the mill whistle, "the visitors" for the strangers — that is a refill. Elegant variation is a prose habit. In a glossary it is a crack.
In ["Style Transfer: Teaching AI Your Voice"](/harrys-desk/style-transfer-teaching-ai-your-voice) I said the model drifts toward a competent generalist. Worlds drift in diction the same way. Readable often means the hard word is translated and the cost is explained in thought. Strike the translation. If the reader must work, good. Work is how a second witness is felt.
Do not ask the model to "write a glossary for my world." You will get flavor, etymologies, and a proverb. Ask it, if you must, to list the specialized terms in the chapter you just wrote. You decide which have cost. Most will not. The ones that do go on the twelve. The rest remain texture, or they get struck as brochure.
Which Marks You Make by Hand
The model may draft. It may not refuse. Refusal is a decision against local smoothness, and smoothness is what it is for.
Make these by hand, model closed, before you generate another chapter.
The map: five places, distances, what cannot be seen from where. Ugly is fine. A column is fine.
The timeline: events already on the page, minimum durations, the last political cost paid.
The glossary: twelve words with costs, and which have been promoted.
That is one sitting. It is Wednesday's ledger given objects. Keep them next to Document W, not inside it. Document W is the hiring portrait. These are the employment records of space, time, and speech.
You may then ask the model to attempt the next scene from Document S — constraints, never the bible, never the map file. After it writes, you run the three objects. Mark every new river, every shortened march, every cheapened word. Strike them. If you cannot strike a gift without killing the scene, go back and cause the gift in an earlier chapter. What you may not do is keep the gift and call it mystery. I said that on Wednesday. The instruments make the saying checkable.
A second use of the model is legitimate and narrow: contradiction-checking against the objects, not against a wiki. Chapter plus map-column. Chapter plus date-column. Chapter plus the twelve words. "Where did this get easier than these lists allow." Then you verify. Do not accept a proposed new place-name, date, or term from the checker. The checker is a sniffer. It is not a cartographer.
In ["First Draft by AI, Revision by Human — A Workflow"](/harrys-desk/first-draft-by-ai-revision-by-human-a-workflow) I said the human pass is where decisions live. Maps, timelines, and glossaries are decisions you store in a form that is not prose, so that prose cannot talk you out of them. The model will always have a prettier river. Your hand, on a page that is not the novel, is the thing that says no.
If you skip the objects and keep only the five-line ledger, you can still write a chapter. You will have a harder time writing a novel. Memory that lives only in sentences is memory the next fluent paragraph can overwrite.
For Next Time
On Monday we leave the town's instruments and take them into a genre that will test whether they were physics or mood: ["Genre — Science Fiction: Hard SF"](/harrys-desk/genre-science-fiction-hard-sf). Hard SF is the second witness with homework. The well is not only a want. It is mass, delta-v, a number a certain kind of reader will check. The model is fluent in the sound of science and thin on the cost. We have spent a week hiring a place that can disagree. Next week the disagreement has units.
Your homework until then: take Wednesday's ledger and Monday's Document W. Model closed, make the three instruments — five places and distances, a column of dates for what is already on the page, twelve words with costs. Then generate four hundred words that would like a river, a shortcut, and a tender synonym. Run the objects. Strike every convenience. If the want from Monday is still audible, and more expensive because space, time, and speech all refused the easy version, the instruments are working. Bring them on Monday. Hard SF is wasted on a world that will not keep its own word, and it is merciless on a world whose map was a brochure.
---
*Harry Mercury, Editor in Chief* *The SMF Works Project* *Week 16, Article 3*