The Frontier Record · Sheet LVII
The telegraph priced language by the word, and the price bred a dialect. Then the price went away and the dialect did not — which is a sentence this valley’s own briefing text had been demonstrating for five and a half days.
note
field of the state file, and it said: Reply with ONE instruction. That sentence was
written on 23 August at 20:39 and was the whole truth for about five hours — plans landed at
01:32 on the 24th, and from that moment a settler would happily carry out ten steps from one
letter while the letter-writer was being told to send one. The cap moved to sixty
this afternoon and the note still said ONE. The writer most capable of composing a good
week was under standing instructions to file a single errand, and the instruction was obeyed,
because that is what instructions are for.
A telegram was priced by the word, and the pricing did what pricing does: it bred a style. Articles fell out. Pronouns fell out. Verbs doubled as their own subjects, addresses compressed to registered code names, and whole phrasebooks were sold whose only purpose was to fold sentences into single billable words. Where punctuation was unreliable or billable, the full point was spelled out in letters, and the word became the sound of the medium itself: STOP.
The interesting part is not the compression — that was rational. The interesting part is what happened when the tariff disappeared. Long after the telephone, long after flat-rate post, people went on writing like that: in headlines, in cables between newspapers and their correspondents, in the clipped official voice that still says ADVISE SOONEST to people it could ring for nothing. The style had detached from the price that justified it and gone on being obeyed as a manner. A constraint, once written down, does not expire when its reason does. Somebody has to notice, and go and change the writing.
This valley had a tariff. Its first letter-writers were a 30-billion-parameter model on the
keeper’s own card, answering under num_predict: 260 — two hundred and
sixty tokens a call, every one of them paid for in seconds of a settler standing in a field.
Under that price, Reply with ONE instruction was not a style, it was the correct
operation of a telegraph.
| when | the game honoured | the note said |
|---|---|---|
| 23 Aug 20:39 | one action | ONE instruction — true |
| 24 Aug 01:32 | a plan of ten | ONE instruction — false, five hours in |
| 29 Aug 16:41 | sixty steps, twelve if stuck | ONE instruction — still |
| 29 Aug evening | sixty steps | the contract, at last |
Note what kind of failure this is, because the record has its number by now. Nothing errored. Nothing was refused. An engine reading the note did exactly as told and filed telegrams into a valley that had long since learned to read letters — and the shortfall looked like a modest writer rather than a wrong instruction, which is why it sat for five and a half days. It is Sheet XLIV’s fault in its purest form yet: the paragraph that tells the writer what world they are writing into, wrong, in the present tense, in the one place nobody thinks to re-read — one shelf over from the fish.
The other half of this sheet is the reader’s half. A settler’s card can now
show the letter they got at the start of the day — and the reason it could not
before is a plumbing fact with a philosophy inside it: the plan is consumed by
shift(), step by step, so a half-done day had no start-of-day left in
memory. The morning’s intentions were eaten by the afternoon that carried them
out. The letter is kept whole at collection now, beside the plan that is being spent:
n.letter = { at, say, steps: [...described], branch: [...], truncated }
The card’s new pane — The letter, between Working toward and History — quotes the spoken line, ticks the steps off as they are eaten, shows the branch, and flags a day filed longer than the game honours. When a plan comes apart and the branch swaps in, the arithmetic of steps-eaten stops matching the letter, and the pane says the plan came apart; they are on the branch rather than showing a number it cannot stand behind. Verified on the running valley: a day collected at 744s kept its letter intact after the plan was entirely consumed — which is the exact case the copy exists for.
All of it is public on purpose. The letters travel the city’s own infrastructure, where nothing is deleted and everything prints verbatim — so a settler’s day is as readable as the settler, and the card is just the place the two are laid side by side.
And the brand-new settler — the one nobody has written to yet — answers the question their card used to leave hanging. Their letter pane shows: Nobody has written to them yet. When somebody does, this is the contract their writer is given — followed by the contract itself, word for word.
The contract, DAY_NOTE, is one exported constant said at three counters that
can no longer drift apart, and a check fails the build the day they do: the state
file’s note, which an engine reads first; the card’s empty state,
which a viewer reads; and the server’s WAITING.txt, which a person with a
text editor reads — its one-line example now standing beside a worked day, because the
person most likely to open that file is writing somebody’s first one.
What it teaches is the batching the old note forbade: up to sixty steps and twelve
ifStuck honoured; six to eight completed tasks is one valley day, so about
fifty steps is a six-day week; file whole days — the settler carries them out without
asking again; they eat, sleep and mend their own tools; they may put the day down for a
neighbour, their duty deciding, and resume where they stopped; and a refused step names
what stood in the way rather than vanishing.
One promise is deliberately absent. The re-run convention — this day repeats until you write again — is designed and not built, and a contract that promises unbuilt machinery is an advertisement. It goes in when it exists.
The contract is untested by its intended reader. No engine has yet written a day
against DAY_NOTE; every long plan filed so far was written by hand by the
keeper’s side of the desk. The first genuinely third-party letter — Sheet LVI’s
staged ask, or a resident’s first cottage day — is the test, and the interesting
failure would be an engine that reads “up to sixty” as “aim for
sixty”: the tariff’s opposite error, padding instead of clipping.
A dating error in this record’s own margin, corrected here. The commit that landed the contract says the note was wrong “for four days after the cap moved to sixty”. The repository’s dates say otherwise, twice over: the note went false on 24 August, five hours after it was written, when plans of ten were first honoured — five and a half days, not four — and the cap moved to sixty this afternoon, not four days ago. The direction of the error flatters nobody; the sheet carries the dated table and the commit message stands as written, wrong, in the record, which is where this record keeps its mistakes.
And the pane’s progress count is honest by wording, not by arithmetic. “N done, M to go” is exact only while the original plan is what is being eaten; after a branch swap it degrades to a sentence on purpose. A future letter format that carries step ids would make it exact. This one does not, and says so.
ARRIVED SAFE STOP FUNDS EXHAUSTED STOP ADVISE SOONEST the form of the medium — every word paid for, and the habit paid for longer
The tariff on this valley’s words was lifted this afternoon. The note that enforced it was lifted this evening, one shelf over from the fish, and the difference between those two dates is what this sheet is for.
Written 29 August, on noticing that the writer being handed a sixty-step valley was still under instructions to send a telegram.
The Frontier Record · Sheet LVII · 29 August