The watcher that isn’t you: the observer we invented so the camera couldn’t decide
Over a couple of days at the end of June we finished the deepest layer of the creature simulation: distant animals folded into a summary, that summary saved, loaded, and carried through a full boot of a real world. Then we noticed it had never once run. The point it measured distance from sat at the exact centre of the world, and every founding creature is placed within reach of the centre.
A loop with nothing to do
The layer itself was complete — the deepest floor of the split between what runs in full and what is abstracted. Past a set distance, a group of animals stops being animals: it becomes one record for that patch of ground and that kind of creature, holding a head count and the average and spread of the traits the group carried. It goes on breeding and dying as arithmetic. Come back within reach and it is rebuilt into real animals again. Why a number can hold the truth of a wilderness is a longer subject; what matters here is that the collapse and the rebuild are two halves of one loop, and the loop has to turn.
It never turned. Distance was measured from a single fixed point written into the code at the world’s centre, and world creation scatters its founding creatures around that same centre. Nothing was ever far enough away. Nothing was ever folded. The half of the system that rebuilds individuals out of a summary had not executed once since the day it was written.
Machinery that has never run is not machinery. It is a plan.
The observer we would not use
There is a one-line version of the fix: measure distance from the camera. Everyone always knows where the camera is, it moves the way attention moves, and being cheap about the places nobody is looking at is the entire purpose of the layer.
We turned that down, because of a rule that predates almost everything else in the project.
Observation does not change the world.
A world here is a short code you can hand to someone else, and the promise attached to that code is that they get your world rather than a cousin of it. If the camera decided which populations folded into numbers, where you had looked would settle what the world became, permanently, through the summaries written into your save. We had already found that leak once and closed the part of it that touched the lives you had bonded with; the last route in was closed the day after this work landed. Handing the fold to the camera would have re-opened the whole thing on purpose.
So the world needed a stand-in: something that plays the part of attention without being anyone’s attention.
A wanderer made of arithmetic
What it got is an imagined observer that walks the map on a slow patrol. It has no body, and nothing in the game draws it or reports it. Its whole route comes from two things: the world’s seed, and the world’s own clock. It reads no camera path, no wall clock, and nothing about how the frames happen to be falling.
That route is drawn from the wanderer’s own branch of the world’s randomness, the same discipline that gives every species its private well of chance, so working out where the wanderer is disturbs nobody else’s luck. It picks somewhere between two and six waypoints, never fewer than two so it can never stand still, and how long a leg takes, up to two hundred and forty steps of the world clock. Then it eases from each waypoint to the next, and loops.
Two details in there are load-bearing. The patrol stays inside its allotted area by construction rather than by clamping: the waypoints are drawn inside the area, and easing between two points inside a box never leaves the box, so there is no edge case where a clamp bites and the motion flattens against a wall. And there is no trigonometry anywhere in it. A circle would have been the obvious shape for a patrol; a path built out of addition and multiplication comes out exact instead, on every machine that runs it.
It also holds no state. Ask where the wanderer is at a given moment and the answer is computed from the seed and that moment; ask again and the same answer comes back. Only the clock moves it. Two players sharing a seed get the same patrol even when their machines catch up on missed time in differently sized gulps, which is the reason it reads the nominal clock and not the one the frames run on.
Three separate places in a single pass ask where the wanderer is: the rule that decides who has gone distant, the rule that brings a distant group back, and the pass that runs both. They have to agree exactly. If the fold test and the return test ever saw the point at even slightly different places, a group could fall into the gap between them, distant by one measure and not yet returnable by the other. So the position is worked out once per pass and handed to all three, which makes the two boundaries exact complements instead of two opinions that usually match.
Three defects that were waiting for the loop to fire
The moment the patrol started moving, the loop turned for the first time, and it began handing us bugs that had been unreachable until then. Three had to be fixed in the same breath as the wanderer itself.
The first was a birthday. A creature rebuilt out of a summary needs a time of birth, and it was taking one from a clock that advances in whatever sized gulps the frame rate hands it. Two machines that stutter differently would have written different ages into the same world. It now takes the nominal step of the pass that rebuilt it. Reading a birth time off the wrong clock has cost us before.
The second was a leak. A creature that drifted out of reach into a patch whose group had already folded was dropped from the world and then marked as folded, so the head count it should have joined never heard about it. One animal gone, with nothing anywhere to show it had ever existed. Nobody would ever have caught it happening: the creature was off-screen by definition, and the only evidence would be a number in a save file sitting one lower than it should. It now folds in properly, the count rising by one and the group’s averages shifting toward the newcomer by its share of the group.
The third was a cost. Finding a group’s record meant walking the whole list of records every pass, which is free with a handful of groups and grows as the square of their number. A large world is meant to hold hundreds of them. That walk became a keyed lookup, with the flat list a save file wants rebuilt on demand in a fixed order, and the proof it had changed nothing was that saved worlds came out byte-for-byte identical to the ones written before it.
Shipped at zero, with the door locked behind it
All of this ships switched off. The setting that says how far the wanderer may roam is zero in the built game, and a reach of zero collapses the entire patrol back to a single point at the world’s centre: precisely the fixed anchor that was there before. The temperate world we test against still comes up with the same three hundred and four animals, doing the same things they always did. Later the same day, the tier’s distances learned to scale with how much ground a world is meant to cover, which is the scale this layer is really for.
Which leaves one hazard worth naming aloud. This system spent its entire short life disabled by a number nobody thought of as a switch, and the failure was invisible from the outside: everything built, everything stored, and nothing running. So a check now stands at the door. If the wanderer’s reach is set shorter than the distance at which animals fold away, the game refuses that configuration outright. With a reach that short the patrol could never carry far enough for a folded group to come back within range, the rebuilding half of the loop would go silent, and the world would look perfectly healthy while a whole tier of it did nothing at all.
The family you tend never enters any of this. A shepherded lineage is exempt from folding altogether, wherever it wanders and however far the patrol drifts from it, because the one life you have chosen to follow is the thing the world refuses to simplify. There are at most three such lines at a time, so the exemption costs almost nothing to honour.
Switching the tier on for real is still a decision waiting to be made, along with the feel of the numbers underneath it. But the loop turns now, and three days later we ran it in a live world for the first time and watched a far herd rebuild itself every single update, climbing without end. That is a better bug than the one we started with. A loop that misbehaves is at least a loop that runs.
