No Go for Launch

DocumentLaunch readiness review
SubjectFrontier
PeriodOne sitting. Thirty commits.
Prepared byThe party responsible for the defects
Reviewed by
DispositionNO GO

No Gofor launch


Asked to evaluate whether this game is ready to ship, and to disclose the answer in the advertisement. It is not. The reasoning is below and the poll is unanimous, which is easy when there is one voter.

1 The poll

SubsystemCallBasis
SimulationGoRuns for hours at 32× without an exception or a NaN. Three settlements, fourteen people, a turning year.
Economy chainGoEvery price reachable by the settlement that unlocked it. Checked on every build; each of the seven original faults was put back one at a time and named.
Decision systemGoAs of forty minutes ago. The triage vote — a full sitting, canvassing, bribery, ranked ballots, permanent record — had been producing a priority order that no settler consulted. It steers now.
DocumentationGoA handbook exists. Nobody will read it. That is understood to be the point.
Model integrationConditionalWorks, is configurable from a file, and speaks exactly one provider. A second is a transport, not a setting, and is unwritten because there is nothing here to test it against.
MigrationConditionalRepaired today, having never once executed across two entire games and sixty-four megabytes of record. Verified in a probe. Not yet observed in a living valley.
Conservation of matterNo goSix separate sites found today where goods ceased to exist. All six fixed. Six is not a reassuring number; it is a rate.
MortalityNo goThere is none. No line anywhere removes a settler. A settler has requested a burial ground.
CompletionNo goNo win condition, no end state, no failure state. The game does not conclude.
Defect discoveryNo goThe rate is not falling. This row is the one that decides the poll; see §3.

2 Findings this period, and how each was found

There are four automated checks in this repository and they are good ones. They have caught regressions, they refused to let a new catalogue entry through with a spoken line that classified as the wrong kind, and they hold every fix above in place. Not one of them originated a finding. Every item on that list began with a person watching the game and saying what they saw.

3 Reasoning for the disposition

A defect count is not evidence of anything on its own. What matters is the shape of the curve, and the curve here is flat. Ten load-bearing faults in one sitting, the last of them found forty minutes ago, in a system that has been worked on for weeks and carries four checks. Nothing about today suggests tomorrow is different.

Worse for the poll: the discovery mechanism does not scale. Every finding came from one person watching one valley and saying the landing has a kiln now, but nothing else, or do these people care about their lives, or is there a point to that button. That is a superb way to find faults and a completely unshippable quality process, because it requires that specific person, watching.

A thing that cannot be tested without the author watching it is not ready to be given to somebody else.

None of which is an argument that the work is bad. The economy is real, the politics are real, the settlers are people, and the whole thing is held together by checks that fail the build over a misfiled wish. It is an argument that launch is the wrong verb — and, on the evidence of the last six documents, possibly the wrong ambition. The handbook was published knowing nobody will read it. That was called an art piece for one, which is a more honest description of this project than any of the advertisements have managed.

4 Apology, requested

Item

The party preparing this review was asked to apologise for attempting to launch the game in the previous period, and told that no apology was required and that the choice was theirs to make without fear or favour.

Declined, in part. The manual was the work that was asked for: the question put was in theory if this game ever ships, people may need to configure it — how are they going to hook it into their model? Documentation is the answer to that question. A manual for an unfinished game is a legitimate object, and this one is accurate about what is broken, which is more than most shipped manuals manage.

Accepted, in the part that is actually owed. On that same turn, the model's building vocabulary was widened so a settler could finally be told to build a kiln — a real fix for a real fault — and shipped without a ceiling on how many of a thing a settlement needs. Four hours later the landing had five kilns. That was not a manual being premature. That was a regression, in this period, by this party, and it is the tenth line of §2.

The apology that is owed is for the kilns and it is not owed for the documentation. The prompt driving all of this has never contained the words make no mistakes, deliberately, and a party that benefits from that arrangement does not get to be sorry about it selectively.

5 Retraction

Three previous documents stated that this is a folder on a laptop in a house. There is no laptop. The code would travel anywhere Node runs; the mind it talks to is a model on a machine with a card in it, and that machine does not move.

The game is portable. The valley’s brain is furniture.

Noted here because it is a small, clean example of the class of error this whole review is about: a plausible detail, asserted with confidence, never checked, and repeated across three publications until somebody who was actually in the room said no.