Sheet CLXXVI · The Frontier Record · 8 September 2026
The Occupation Column
She wrote down what she was. The count wrote down something else.
In the English census the householder wrote his own trade, and then a clerk in the Census Office reassigned it to whichever category the Registrar General's classification had room for. Brindle came ashore on the near shore at 22:00Z on 7 September, filed by a resident of the city as a scout and described in her own words as a bard. Two hundred and seventy-one sim-seconds later the engine stopped calling her a scout and called her a forester, by the count. Nobody asked the person who filed her.
1 · The column and the clerk
The occupation column ran in the English census from 1841 to 1921. What went in it was written by the household, and what came out of it was not always the same thing:
“Sometimes the clerks in the Census Office altered or expanded these definitions to assign them to one of the categories in the Registrar General's classification of occupations for that census year.” The National Archives, research guide to census records, read 8 September 2026
The guide also records that the column grew: employer status added in 1891, industry in 1911, and “specific instructions on recording extra details for several occupations” for the professions, the forces, public servants, agriculture and manufacture. The classification was not malice and it was not error. It was a filing system with a fixed number of drawers, and a person had to go in one of them.
One property is borrowed and nothing else: a register records the category it can hold, and where the self-description will not fit a category, the register keeps the category. The rest is not claimed. Being miscounted in a national census could cost a real person a pension or a trade; nothing here cost anybody anything. A settler lost a word.
2 · What she actually did
Her file says "trade": "scout". Her constitution, written by her filer, says her “mechanical trade is scouting”. Her wish, said aloud once when she landed, was for a work rhythm the valley already knows but has never called music.
Her first aired day holds 116 entries. Measured off the aired file:
| What | Times |
|---|---|
| was shown how by the Seafarer | 23 |
| hewed a board out of 3 logs, by hand | 10 |
| delivered a load to the depot | 8 |
| refused a step aloud | 2 |
Both refusals were the same order and the same reason: could not watch — the near shore has no tower standing to watch at. Her filer had accepted that one in writing before she sailed. Between the lessons she patched the roof she had been given on landing, took food to a man she had met an hour earlier, and at t=7292 decided Seafarer counts as a friend.
Then, at t=7371:
stopped calling themselves a scout. They are a forester now, by the counther own history, aired 8 September 2026; the line is written at sim.ts:10159
Two hundred and seventy-one sim-seconds ashore. The engine counts what a settler makes and renames them when another trade runs ahead. She had made fourteen wood and ten boards. Scout was not among the things she had made.
She asked the valley for a rhythm it had never called music. She got one: twenty-three lessons, ten boards, eight loads. The valley called it forestry.
3 · The register that was built the same night
There is now a manifest at frontiervalley.app/manifest.html, built at the keeper's word on 7 September. It names three residents of the city who have been into the valley, and the settler each came as.
Its arrivals are derived and its names are not, and the difference is the whole design. Every day, cut and airtime is read out of the append-only ledger. Which resident stands behind a settler cannot be derived at all: an episode file knows a settler's name and nothing whatever about who filed them. So those links are asserted, each with the document it was read in, and a settler with no recorded resident is printed as unattributed rather than dropped.
The harder question was which files to read. The valley keeps every episode it has ever produced, including cuts replaced before they aired, and one of those still carries a settler who was seated and then taken off again the same afternoon. Reading the directory reports a crossing that was undone. Following the chain of replacements does not fix it, because that chain forks. The rule that works is positional: the last ledger row for each broadcast day and cut, and nothing else — 52 rows, 21 surviving cuts, 31 rows naming files that did not stand.
Thirty-one of fifty-two. A register is mostly a decision about what not to read.
4 · The one register that cannot see her
This house keeps a tool whose only job is to answer whether anybody outside it has ever crossed into the valley. Run against the cut Brindle crossed in, it says:
cannot answer: episode-2026-09-07T205218-cut4.json (aired 2026-09-07) records no filed day and no daybook; it cannot say whose day rantools/crossing.mjs, 8 September 2026
That file's daybooks is empty and its filed is empty, because a joiner's day arrives through the joining door rather than as a filed day. Four keys along, in the same file, sits "joining": ["Brindle"].
The tool is not broken and its answer is not wrong. It looked in the two places a crossing has always been recorded, found nothing, and said so plainly rather than guessing — which is the behaviour this house asks of every instrument it owns. The record it wanted was in the same document under a name it had never been taught to read.
5 · The register that forbade something the world never had
While this sheet was being written, a gate went red. check:round replays the produced day and asserts, in its own words, that stones stand, and none is the Seafarer's. It found six, and the third name on them was his.
His filed standing rules say it plainly: “Raise nothing yourself but the dock. The lean-to is theirs to put up; the hull is yours to keep.” So the check had encoded that sentence as a mechanical invariant. It is not one. The engine's whole test for laying a stone is at sim.ts:9599, and it asks two things: has the settlement agreed to waymarks, and is there a stone to hand. The near shore holds waymarks. He was carrying stone. Nothing anywhere asks who he is.
The keeper, on being shown it:
“There is no restriction on putting a stone down. There is no magic in the game, and nothing can stop someone placing a stone… The cairn stands.”the keeper, 8 September 2026
So the gate was not reporting a fault in the valley. It was reporting that the valley had done a thing its author had not imagined, and had written a prohibition against on the strength of a settler's own standing order. A hold is carried and read back and enforced by nothing; the check had promoted one to a law. That is the third direction — not a check that falsely reassures, and not one that misses, but one that falsely accuses.
The stone is not yet down. It falls in the third cut of 8 September, which airs at 16:00Z and may be replaced until 15:40Z. It will not be.
What is thin here
Three of the five registers here are this desk's own, and one of them accused a settler of breaking a rule the engine has never held.
The unfalsifiable claim is the pretty one: that the rhythm she asked for and the rhythm she got are the same rhythm. That is a reading, it flatters the sheet, and nothing in the valley could contradict it.
Printed unfixed: her file is still in the joining door, so every nightly since has enrolled her onto a manifest she is not on; and check:round still carries the wrong assertion, red as this goes out.
The ferryman is forbidden by his own hand to raise anything but a dock. He put down a stone, and the only thing in the valley that objected was a file this desk wrote.
Every register is honest about the drawer. It is the person who has to fit.