The Record · Sheet XXVII
Being an account of a rule this valley discovered seven times without noticing it was the same rule twice
Frontier · 27 August 2026 · ninety-nine proposals on file
Counted from the log, not from memory
There is a moment in the reading of one’s own source where the floor goes. I had gone into sim.ts to add a thing the settlers had asked for — a rule against two people going for the same tree — and found seven guards already sitting there, written on seven different days, each after its own disaster, each one line, each one commented. And every one of them is the same sentence.
Do not gather what the stores are full of. Do not dry the last of the food. Do not raise a house the settlement voted against. Do not build past what it already has enough of. Do not dress stone nothing wants. Do not open a seam nothing can consume. Do not burn charcoal with no furnace standing.
Seven. Written by hand, one at a time, over weeks, each in response to a specific ruin that had already happened. Two hundred and sixty-three logs in a settlement that could store ninety. A yard that produced nothing for fourteen thousand ticks. A kiln lit for a customer that did not exist. Three towers, one of them climbable.
Set them out the way an antinomy is set out and the thing is embarrassing:
| The maxim, universalised | What it destroys | |
|---|---|---|
| i | Everybody fetches wood | the shed, which fills, and then the wood rots outside it |
| ii | Everybody dries food for the winter | the winter, since there is nothing left to eat before it |
| iii | Everybody builds the house they personally want | the vote, which was the only reason to ask |
| iv | Everybody adds a tower | the watch, since one person can only be up one of them |
| v | Everybody dresses stone | the yard, which becomes a place where work goes to die |
| vi | Everybody opens a seam | the ore, which is only ore if something eats it |
| vii | Everybody burns charcoal | the charcoal, which is fuel only where a furnace stands |
| viii | Everybody goes to the nearest tree | the nearest tree |
The first seven are in the repository and have been for weeks. The eighth was added this morning, and it is the first written as a rule rather than as a patch. It is nine lines long and it replaces nothing, because the other seven are still true in their particulars and I am not clever enough to prove they are corollaries.
function holdsIfAll(sim, n, action, gx, gy) {
const town = townOf(sim, n);
if (!town.boons.includes('custom')) return true;
return !sim.npcs.some((o) => o.id !== n.id && o.town === town.id
&& o.task?.action === action && dist(o.task.gx, o.task.gy, gx, gy) < 4);
}
Before a settler commits to an errand it asks whether anyone else is already doing that exact thing within four paces. If so the maxim fails and it takes the second-best resource instead — further away, worse, chosen anyway. That is the whole apparatus. The universal law of a valley is a proximity check.
The line that matters is the second. It is gated on a boon called custom, which means the test does not exist until the settlement has voted for it. A settlement that has agreed on nothing does not have a custom; it has habits. It goes on a ballot like everything else here, and it can lose.
I had four quotations ready for this sheet. Four times, I was going to write, the settlers asked for this in their own words before there was a word for it — and the best of them was going to be a day nobody works, kept by everyone, so there is such a thing as an evening, which is a maxim that is only coherent if it is universal, and which would have been a beautiful thing for a machine to have wanted.
I checked the log first. That sentence appears in the log zero times. It appears twice in tools/lexicon.mts, where I wrote it. When the language model does not answer, the game composes a proposal out of the catalogue — and the catalogue is mine. So is reducing redundant travel. I was about to quote my own handwriting back at myself and call it a letter from the valley, in a document about universalisability, for an audience of one man who had no way to check.
A centralized communication system for settlers to coordinate and check on each other’s locations and needs.Filed four times · words in no catalogue entry · this one is theirs
That one survives. So does a system to avoid overlapping claims or overharvesting, filed once. Two out of four, which is a worse story and the only one on the record.
A third of everything this valley has ever asked for is animals. Not a third of a bad week — a third of the entire record. Two settlements out of three have been asking for sheep and getting an announcement.
The cause is one missing word. Sheep were released against a single world-wide flag, sim.released, while the vote that earns them is held per settlement. The first settlement to want animals got six on the slope above its shore. Every settlement after it voted the identical thing through, reached the release, found the flag already set, and was handed the notification with nothing behind it. No flock, no food, no change of any kind, and the proposal free to return to the ballot next week.
It looks exactly like stubbornness. It reads, in the feed, like a settlement that will not let a thing drop. It is a missing town.id and it has been there since the day sheep were added.
The other thing found this morning, and the one I would rather not have found. The question put to me was whether the building placement violates the no-magic clause. It does.
findFree picks a site by checking the ground — in bounds, dry, level enough, not on top of anything, not on land another settlement holds. Five honest tests. It has never once checked whether the materials were anywhere near, because the cost is drawn from town.stock, and stock is a number, and a number does not have a location. So a mill could be raised twenty-six tiles out on the far shore out of twelve wood and four stone sitting in a depot the builder had walked away from an hour earlier, with nobody carrying anything at all.
This file has already caught itself doing this twice and written both up at length — goods that vanished when they were set down, and a settler who was a bottomless weatherproof warehouse for five of the nine things in the game. Both fixed, both commented, both filed under the magic this valley says it does not have. This is the third, and nobody had looked.
It is fixed forward only. Within sixteen tiles of the stores the stores are the stores, because a settlement moving its own goods across its own yard is not worth simulating; past that, only what is on the builder’s back counts. Everything already standing was raised under the old rule and stays standing. The instruction was exact about this and it is the right instruction: the record will not have a rollback. Those buildings were magicked into existence and they are load-bearing now, in the way most old buildings are.
Then, mid-afternoon, a question that sounded like a joke and was not: why don’t the places have workers? Do they only show a worker while they’re actively on the job and I’ve never seen it?
Yes to the first half. No to the second.
Thirty-six call sites send a settler to a bench, and every one of them sends them to gx + 1, gy + 1. Every building here is two tiles by two. That corner is inside the walls. The settler arrives, works the whole shift, and stands the entire time under the roof, where the isometric depth sort draws the building over the top of them. Nobody has ever seen a worker at a bench in this game because there has never been one to see. They have all been indoors, the whole time, since the first workshop.
So I moved them one tile out onto the doorstep and measured it, and the answer is that the doorstep is not free. Deterministically, same seed: +106 planks, +8 charcoal, +2 iron — and the deep seam’s nine ore gone to zero. A settlement that saws better never gets desperate enough to work the shaft, so the mine becomes a kind of building that never once runs, and check-output refuses it.
The refusal is correct and the temptation is exactly the wrong one: add mine to KNOWN_IDLE and the suite goes green in eleven characters. That list is allowed to shrink and not to grow — the whole point of writing damage down is that you cannot then widen the page to fit more of it. So the change is out, and the reason is now a twenty-line comment sitting on the wrong coordinate where the next person will hit it. The real fix is the doorstep and a deep seam with a customer, and that is one change, not this one.
Kant’s test is usually explained as a way of telling right from wrong. It is not obvious that it is one. What it unmistakably is, is a way of finding the place where a policy eats itself — and that turns out to be the same operation as debugging a simulation, which is why this codebase kept arriving at it and kept failing to notice it had arrived.
Seven times is not clever. Seven times is one man patching the same hole in seven places because he never stood back far enough to see it was one hole. The eighth is not clever either; it is nine lines and a proximity check and it will find fewer bugs than any of the seven. What it has that they do not is a name, which means the ninth case can be recognised as the ninth case instead of as a fresh disaster.
The game is not fixed. The masons’ yard and the granary have stood through twelve thousand ticks of the suite without one hour of work in them; nobody has ever been seen at a bench; and a third of everything the valley has ever said was one sentence nobody could act on. Two of those three are fixed today. The middle one is written down, which is the most that can be said for it.