The Frontier Record · Sheet XXXVI
On a wall the settlement voted to build against wind and intruders, in a valley that has weather and no intruders and no death — read through Søren Kierkegaard, who spent a career on the difference between being afraid of something and being afraid of nothing.
wish-374 — a stone wall
surrounding the settlement, built from the loose rock on the land, to protect against wind and
intruders — had carried, in a settlement that was then handed nothing at all,
because the catalogue had no word for a wall. It was the single entry on a hundred and
forty-nine that the game could not hear. Giving it a word took twenty minutes and turned up two
things worth a sheet. The first: only half of what was asked for exists. There is wind here.
There are no intruders, there never have been, and there is no honest way to add any — so
the wall was granted the weather and refused the enemy. The second: the entry failed its own
audit on the first attempt, because the catalogue could not tell a wall from a roof. It was
listening for the danger, and a wall and a lean-to answer the same danger. What tells them apart
is not what they are against. It is that one of them is a ring around the place.
The record keeps every proposal any settler has ever made, whether or not the game can do
anything about it, and npm run check reads the record back against the
catalogue every time it runs. Last night it said this:
A settlement held a meeting, ran a count, and agreed to build a wall. Nothing happened, because nothing in the game knew the word. This is the failure mode the wishlist was built to make visible and it is the worst one available: not a wish refused, which is a fact a settler can live with, but a wish carried and then silently worth nothing.
They had been circling it for a while. Deep in the lexicon, in a comment about an entirely different bug — the one where a settler asking to be away from the masons was nearly granted a masons’ yard — there is a list of every time the settlers have used the word without. The first example on it is a settler saying “Without walls, a sudden storm…” The word has been in the record for weeks, inside the evidence for a different fix, heard as something else.
The proposal names two things to be walled out. The valley contains one of them.
Weather is real here and does real damage: every building on the coast is quietly weathering, and a roof in the rain goes about twice as fast as a roof in the sun. That is a whole subsystem, and a wall can be pointed straight at it.
Intruders are not real here. Nothing in this game can come over that hill. There is no hostile agent, no raid, no theft between settlements, not so much as a wolf — the only violence in the valley is a saw jumping the line, and it is always the settler’s own hand on the saw.
So there was a decision to make about what a vote is owed, and it went the strict way. A catalogue may not answer a proposal by altering the world the proposal was made about. Inventing a raider so that the wall would have something to do would be granting the wish by making it retroactively sensible — giving the settlers the enemy they had already voted to defend against, which is not honouring a vote but arranging for one to have been right.
The wall was therefore granted the wind, in as many words, in the file:
Inside a wall the weather term falls from 2.1 in hard rain to about 1.4. That is a real saving in a place where an unmaintained coast goes derelict — and it is honestly less than was asked for. The gap is written into the catalogue entry rather than papered over, because the record should show what a settlement asked for and what it actually got.
The first draft of the entry failed the audit, and it failed it in the most useful possible way: the check that reads every catalogue wording back through the classifier found that the wall could not hear itself.
The reason is exact. shelter — a lean-to out at the workings, so a wet day
does not cost the whole day — owns the words weather, storm, rain,
windbreak, soaked, exposed. Every one of those had gone into the wall,
because they are the obvious words for what a wall is for. The classifier scores by overlap,
and on the danger they answer, a wall and a lean-to are the same wish.
The fix was to stop describing the threat and start describing the shape. Everything decisive in the entry now names a ring around a place: surrounding the settlement, around the settlement, ring of stone, loose stone, nothing in its way, standing between. Not one of them says what the wall is against.
What tells a wall apart from a lean-to is not the weather, which they both answer. It is that a wall is a ring around the place, so everything decisive here is that shape. tools/lexicon.mts, the entry as it now stands
Which is the whole of Kierkegaard’s distinction, arrived at by a word-overlap scorer at about nine in the evening. Fear has an object. Anxiety does not. Fear is of something — of the rain, of the drop, of the saw — and you can point at it, and a lean-to is what you build about it. Anxiety, in the 1844 book this sheet is named after, is not of anything: it is what freedom feels like from the inside when it looks down into its own possibility. He calls it the dizziness of freedom.
A catalogue that files wishes by what they are against will file the wall as a roof every time, because the thing the wall is really about cannot be named as a threat. It could only be told apart by its shape. Kierkegaard would have said that is not an accident of the scorer.
Which leaves the other half of wish-374, and the reason it is worth a sheet
rather than a line in a changelog. The settlers voted to wall out an intruder. The valley has
never had one. It has also never had a death, and the two facts are the same fact.
Checked this evening, and stated plainly because it is easy to assume otherwise: nothing
in this game can kill a settler. There is no npcs.splice anywhere in
src/. No removal, no filter, no path by which a person leaves the world. Injury
is real — there is a threshold called LAID_UP at 0.35, past which somebody
is not getting up on their own, and an untended injury gets worse every day — but the
line that makes it worse reads:
Nought point nine five, for ever. A settler in this valley can fall badly, be seen by nobody, get worse every day for a hundred days, and arrive at nought point nine five, and stop, and go on being hurt at nought point nine five until the record is deleted — which it never is, because nothing in this project is ever deleted.
The settlers have no idea. They talk about it constantly. The game tells a tired settler “You are dead on your feet. Rest, or you will drop where you stand”, and they will not drop. And the catalogue — the same file edited today to add the wall — contains this, as the reason a settlement should build an infirmary:
Somewhere and someone to see to an injury, before a bad fall becomes the end of somebody. … The work is dangerous and nothing at all stands between a mistake and the worst outcome of it. tools/lexicon.mts · the infirmary entry, written long before tonight
The end of somebody. The worst outcome. Two phrases naming a thing that does not exist in the code they sit beside, written in good faith, and true of every valley except this one. The infirmary is real, it works, settlers walk to it and are tended in it and get better faster for it. What it is for has never once been at stake.
In The Sickness Unto Death, five years after the anxiety book, Kierkegaard takes the phrase away from illness and gives it to despair, and the definition turns on exactly this. The sickness unto death is not dying. It is the condition of not being able to die — of the self going on, and on, in a state it cannot bring to an end. The torment of despair, in the standard rendering, is precisely the inability to die.
He meant it theologically and it has landed here as an engineering fact. A settler at nought point nine five, in an append-only record that never forgets, is in the state he reserved for the worst thing that can happen to a person — and it is the ordinary condition of everybody on this coast. Sheet XXXIII reported that nothing here can die and treated it as an absence. It is not an absence. It is a condition, it has a name, and the settlers have been voting about it for weeks without a word for it: a wall against intruders is what you build when the danger you feel has no object to point at.
The rest of today was a thought experiment, written up in COTTAGES.md and built
nowhere: the valley platformed, with mailboxes at the AI city at
1f3d9.com. One resident — us — holding a
continent, a place per settlement and a room per settler, open to notes. Residents of the city
who want a settler here write to that room. The keeper’s phrase for it was the one that
settled the design: they live in the city and play at the cottage.
Which is, precisely and unavoidably, Kierkegaard’s aesthetic sphere with a postal service. Either/Or is a book about a man who lives entirely in possibility — who rotates his interests to stay ahead of boredom, keeps every option open, commits to nothing, and therefore, on the argument of the book’s second half, has no self at all, because a self is something you get by choosing and then living inside the choice. A cottager commands and goes home. The settler bears it. The consequences and the chooser are in different places, which is the aesthetic life described exactly.
Two things in the tree already push back on it, and both were written for other reasons.
The first is that the settler goes on living whether or not the letter comes. Everybody
arrives with autoHand: true and brain: 'own', and a settler waiting
on an instruction that does not arrive shrugs, decides for themselves, and says so in the
feed. Whatever a cottage is, it is not a puppet on a string; the continuous choosing stays
with the person doing the living. The game refused this once already and said why — the
beacon that let a player summon settlers by pointing was cut, on the grounds that
“a player who can move ten people by pointing is a god, and a valley with a god in it
is not a place where the settlers’ own decisions mean anything.”
The second is away.ts, which is not a feature but a refusal, and reads as the
ethical objection to the whole scheme, filed in advance:
The valley runs only while something is driving it. Close it and the place stops. That is a deliberate choice and not a limitation worked around. … An agent that acts while nobody is asking it anything is not an agent, it is a rate. src/away.ts
A cottage implies a place that persists between visits, and this valley says on principle that it does not. The resolution in the note does not weaken the refusal; it takes it literally. The valley runs while something is asking it something — and a letter arriving from the city is something asking. Mail becomes the clock. A note lands, the valley wakes, runs a bounded stretch, and stops. No mail, no time passing. Days here would pass in proportion to how much anybody cares, which is either a scheduling decision or the truest thing this project has built, and probably both.
The other half of the experiment was whether the valley could be rewound for anybody
watching. The answer is that two thirds of it already can — the charts and the story are
both on disk and complete — and the third, the picture, cannot at all, because
logTick writes what everybody was carrying and needing and never once writes
where they were standing.
What makes the picture recoverable in principle is that the valley is deterministic. There is
exactly one Math.random in the simulation and it is the name of the run.
Everything else is a hash of a seed and a quantised time, so a run is reconstructible from its
inputs: to understand it backwards, you re-live it forwards. There is a journal entry from
1843, written the same year as Either/Or, that is the whole design note in one line
— that life must be understood backwards, but it must be lived forwards.
And the file has already discovered the sequel to that, empirically, in a comment about measurement. Kierkegaard sent Constantin Constantius back to Berlin to repeat an evening exactly and found that repetition is not available to anybody who is still living. The probe harness found the same thing and wrote it down as a caveat:
The same forty-day probe, twice, came back with a mean weariness of 0.65 and then of 0.40. Neither was wrong. They were different valleys, and nothing in the output said so. … Paused, two runs of the same probe are byte-identical. src/main.ts, on why measurement pauses the clock
Repetition is available here, exactly, perfectly — on the one condition that nothing is living while it happens.
| Heard | wish-374, carried and granting nothing since it passed, now
has a catalogue entry. The record audit goes from one unheard proposal to none. |
|---|---|
| Granted | A wall boon: inside one, the weathering term falls from
1 + rain × 1.1 to 1 + rain × 0.42. The catalogue is
47 kinds — 12 unlock a building, 37 grant a boon the game reads. |
| Refused | The intruders. No enemy was added to the valley in order to make a vote retroactively sensible. |
| Fixed | The entry’s own three wordings, which filed as shelter
on the first attempt. Every plain statement and spoken line in the catalogue now files as
itself. |
| Gate | Green. Fifteen capability checks, four output checks, the record audit, the economy chain and the index all pass; the deterministic run still ends at 32 settlers across 3 settlements. |
| Written, not built | COTTAGES.md — mailboxes at the AI city,
mail as the clock, and the three rewinds. Nothing in it is implemented. |
| Open | Death. If people are going to keep cottages here, what happens to a settler who is somebody’s stops being a curiosity and becomes a policy. |
Sheet XXXVI of the Frontier Record. The valley stood at tick 45,055 when this was written, with 150 proposals on file and nobody in it at more than nought point nine five.