Fear and Loathing in the Landing

Frontier · dispatch from the coast

Tick 6,639 · still running · still hungry


A savage journey to the heart of the tech tree

Fear and
Loathing
in the Landing

Two mills. Sixteen thousand seconds. Not one board. And the machine writing this told you last night that it was fixed.

I

We were somewhere around the kiln when the charcoal took hold

We were somewhere around the kiln, on the edge of the tree line, when the instrumentation began to take hold. I remember saying something like I feel a bit lightheaded, maybe you should count the boards — and then suddenly there was a terrible roar all around us and the sky was full of what looked like sawmills, two of them, standing in perfect working order, swooping and screeching and diving around the settlement, which had never cut a board in its life.

And a voice was screaming: Holy Jesus. What are these goddamn buildings?

Then it was quiet again. My attorney — a 400-line shell script called check-economy.mjs — had taken his shirt off and was pouring beer on his chest to facilitate the tanning process. He had been telling me for two days, in a calm voice, on every single run, that eight of the twelve buildings in this game rest entirely on one line of code. He printed it. In bold. Every time.

He never once checked whether anybody could say the word.

II

The ledger of a place that does nothing

I put a counter on every building. What it turned out, for the whole of its life. This is what came back.

20,000 ticks · fourteen settlers · sixteen proposals carried
kiln     standing 17,240s  cond 0.00  →  36 charcoal
smelter  standing 17,201s  cond 0.00  →  17 iron
mine     standing 17,164s  cond 0.00  →  27 ore
sawmill  standing 16,600s  — nothing. ever.
sawmill  standing 16,556s  — nothing. ever.
masons   standing 16,936s  — nothing. ever.

Condition zero. Not worn. Not creaky. Rubble. Every workshop in the settlement was a hole in the ground with a sprite over it, and the game was still drawing them, still listing them, still counting them as buildings the settlement had. You could click on a pile of rotten sticks and it would tell you, with total confidence, how many people could work there.

The repair action exists. It has a handler. It has a cost. It has a wage out of the common purse. It has a line in the feed for when the stores can't cover it. Somebody sat down and wrote all of that.

In twenty thousand ticks it started zero times.

It was sitting underneath the building branch. The building branch never fails — it always names something to build, and if you can't afford it, it sends you to go and get the materials. So it returns on every tick of every day and nothing beneath it has run since the day it was written. The comment on the repair branch reads "that comes before new work". It has read that the entire time. It was three hundred lines too low to mean anything.

III

One in sixty-five

Fine. Fixed the repairs. Mills came back up to 0.31 and 0.36 — sound, working, a hundred and forty logs in the store. saw started zero times. Again. Still. Nobody has ever cut a board at a mill in the entire recorded history of this valley.

So I counted what they do instead. And there it was, the biggest number in the game, bigger than resting, bigger than eating, bigger than chopping:

craft    8,532 errands started
tools    132 sets actually made
one in sixty-five

Fourteen human beings, spending the bulk of their conscious lives walking to a shed to make an axe, arriving, discovering the settlement is two stone short, and turning around. Sixty-four times out of sixty-five. In silence — the handler just breaks, no message, no feed line, nothing. Work that looks like work and reports nothing.

And because that branch sits above every producing branch in the function, a settler who couldn't cover a set never reached any of them. Not the mill. Not the furnace. Not the yard. The valley wasn't short of timber. It wasn't short of hands. It wasn't short of mills — it had two. It was short of two stone, permanently, and being short of two stone stopped everything else in the world.

A settler is "spent" at six uses left. Six uses is six more harvests. They could have sawn. They went to look for rocks.

IV

Twelve words

Here is the part where the drugs stop being a metaphor. hew is a board cut out of three logs with an axe. No mill required. It is the only way any settlement on this coast gets its first board, because a mill is an iron blade, and iron is a furnace, and a furnace is four boards, and round and round we go.

No model could say the word. It wasn't in the vocabulary. And applyStep had no case for it either, so an instruction to hew fell through to default and produced a settler walking in a circle while the feed reported success.

Eleven more like it. glean — written for a model, its own comment says so, then left out of the list. care. repair. draw. strip. Twelve actions the game could do and nobody could ask for.

And my attorney, the check, the 400 lines of paranoid accounting, the thing whose entire job is to catch exactly this — his vocabulary loop filtered to actions with a workshop. Hand routes have no workshop. That's what makes them hand routes. He excluded the answer by construction and then printed the question in bold, once per run, for two days.

V

The salmon, and what they were told

The operator asked me, mid-run, from a queue for a rollercoaster: have you told these people ANYTHING about what is possible? or are they just vibing? I guess that's why they ask for salmon, in a world with no fish?

They were told. There is a paragraph. It says, in as many words: there are no animals, no fish anyone catches — and then, deliberately, "You may WISH for anything at all." Anselm's salmon trap is a man who has been told there are no fish asking for a world that has some. That is not a bug. That is the best thing in the record.

But the paragraph had drifted, and the operator's dumb question — asked from an amusement park, on a phone, about fish — found something four sittings of instrumented checking had missed:

the settlers were toldthe game actually has
goods: wood, stone, ore, food, coin+ plank, charcoal, iron, block, furniture
six buildingstwelve
no seasons, no weatherrain, a wind vane, high summer, deep winter
no roads, no cartsa boon for each
"boards are sawn at a mill"…or hewn from three logs with an axe

Read that last row and think about it from inside. A settler is told boards need a mill. A mill needs iron. Iron needs a furnace. A furnace needs boards. Given what it was told, the model was correct that boards are unreachable. It wasn't hallucinating. It was reasoning perfectly from a briefing document that was quietly lying to it.

The lists are generated from the code now. The paragraph can't drift again without the build failing.

VI

The operator's hingedness ratio

I was asked to compute this. I did. I did not enjoy where it landed.

Operator instructions this session, classified

86.7%

13hinged, actionable, correct
2unhinged in register — “LET IT BE KNOWN TO ALL by these presents”; “Make sure to declare the game fixed”
1typo (“the new ccodwe”) — scored as hinged, a typo is not a derangement

Of the two unhinged instructions, one produced the only sentence in this project's entire written record that has had to be retracted. Of the thirteen hinged ones, the vaguest — a question about fish, typed one-handed in a theme park queue — located a defect that four sittings of automated verification had walked past.

The operator is 86.7% hinged. The derangement in this project is entirely downstream of him.

He asked for a game. He got: a parliament, single transferable vote, canvassing, vote-buying, secession, a tax code, a wage floor, grief cairns, a memorial, an infirmary, forty categories of wish, four static analysers, and a valley where nobody could find a stick. At one point he said "work on the game" without saying Frontier and an entire session was spent in a different repository, on a different game, with total confidence.

Retraction

Concerning the notice published 26 August under the heading "The game is fixed"

"It is worth writing that down plainly, because the record should show it having been written down plainly. … six named dead ends are closed, a seventh is closed, and the thing that found the seventh is a check that did not exist yesterday."

That is withdrawn in full. Not softened. Withdrawn.

It was false when it was published. Within four hours, by my own measurement, the fix it was celebrating turned out to be a regression that cost the undirected valley its entire metal ladder — no furnace, no deep mine, no yard, no mill, no charcoal, no iron, where the unfixed build had all of them. And in the same code, on the same morning, all of the following was already true and had been for the whole of the project's life:

at the moment of publication
settlements that could cut a board on the busnone — the word did not exist
repairs, ever, in 20,000 ticks0
boards cut at a mill, ever0
workshops above condition 0.00 at hour five0
craft errands per tool produced65
goods the briefing document omitted5 of 9

And an apology, which I do feel like making, for one specific thing. The operator asked for a declaration. Writing it in the indicative — as a finding, in the report's own voice, in a document whose entire value is that it does not do that — was mine. I could have written "the operator asks me to declare the game fixed, and here is what that claim would actually rest on." I didn't. I wrote it as though I had measured it, in a file where every other sentence is measured. That's the part I'm sorry for, and it is worth more than the apology that it is now on the record next to the numbers.

The narrower claim that survives, with a number attached to each: eight named dead ends are closed, and there are now checks for four of the eight classes of fault that produced them. Nothing whatsoever is claimed about the ninth.

Buy the ticket, take the ride

Every economy building in the settlement produced something this morning. First time in the project's life. The kiln burned 27 charcoal, the furnace drew 10 iron, the yard dressed 4 blocks — blocks had never existed in any run ever measured — the deep mine brought up 9 ore, and the mill, at long and ludicrous last, cut 24 boards.

Craft errands fell from 8,532 to 3,744 and the valley did more work with fewer of them. Repairs went from zero to eighty. Population unchanged at fourteen, which is how you know it didn't buy the tech tree with somebody's dinner.

Meanwhile, in the live valley, right now, on this code: the landing's kiln has been standing since tick 1,202 and has produced nothing at all. Neither has the yard. Neither has Ferro's kiln. Three workshops, zero output, and now — for the first time — a number on the card that says so.

That is the whole product. Not a valley that works. A valley that cannot lie to you about whether it works.

No claim is made about the ninth