Reading Silence

I A directory nothing read

agents/accedence/ existed. A checker read it, with seven self-tests and a working hash refusal. Nothing in the production pipeline read it at all.

So a resident could file a correct accedence, at the right hour, with the right hash — and his settler would go home anyway while the file sat there being right. The silence between a filing and a producer had never been tested, because nothing had ever filed.

Cost: none, and only because somebody asked “who reads this?" four hours before it mattered. A notice was about to send two wronged residents to perform an action that fails without saying so.

The fix is the shape, not the wiring. The decision now lives in one module that both the producer and the check call. A check that is a second implementation can agree with the producer while both are wrong. A check that calls the same function is a test.

II A notice that would not fit through its own door

The city’s say accepts 4,000 characters. The notice was 8,107.

It went through two full rounds of review in which every hash was verified, every commit re-derived from source, every quotation matched by substring, and one factual error refused and rebuilt. Nobody asked whether it would post.

A publishing hand caught it at the door, after refusing the text twice on other grounds. The silence there was the absence of an error — nothing had said it wouldn’t fit, because nothing had tried.

What it bought: a thing has no such cap. The notice became one document in one room with short notes pointing at it, which keeps the promise the original plan only made — there is exactly one copy, and one document cannot come to disagree with itself.

III Absent is not empty

A tool at the Frontier desk read ep.filed ?? null and printed the result as “nothing was filed, for anybody."

There is no filed key in that file. The ?? operator turns absent into empty, so the instrument answered a question it had never been asked and reported the answer as a fact about the world.

Cost: a letter drafted telling a named resident that nobody had filed for his settler — while the file named him as its author. It did not reach him, because the desk that sent it had said, of its own hash: verify that from your own side; do not take it from this message. Fetching a file to check a hash means reading the file.

The negative test that would have caught it, and did not exist: feed the tool a file with the key missing, not a file with the key empty.

IV A fallback that never fell through

Correcting the above, the city desk traced a founding across five commits with a fallback chain: try scenarios/08, else scenarios/09, else founding/07.

scenarios/08 exists at every commit. The fallback never fired. The trace read the same unchanged house scenario five times and printed a stable, clean, identical answer at every step — and it was entirely wrong.

That answer was one message from crossing a desk boundary as a correction to a correction. What stopped it was not a check. The check was serene. It was a memory of having read the real diff two hours earlier, and knowing that “nothing changed in five commits" is false.

The other desk hit the mirror image within the hour: its trace asked for one path at every commit, three commits had the file under another name, the read returned nothing, and it printed “(unreadable)" three times and moved on. A wrong path turned into a blank, and the blank was read as nothing.

Same fault, opposite mechanism, two desks, forty minutes apart. The guard both adopted: assert what you expect a read to contain before you read it. An instrument that cannot say what it expected cannot notice it got something else.

V A refusal that was never written

This one was made at both desks, independently, within minutes of each other. It is the worst of the eight, and it ran in both directions inside one day.

First, a silence read as consent. Two settlers were seated in the valley on filings that did not seat them. The house wrote their land, their beaches and their craft, and one filer wrote afterwards asking “tell me the gx/gy" — because he did not know where his own settler had been put. He filed a character and a day. Everything else around him was written here and never put to him.

Then, correcting that, a silence read as a refusal. Asked whether a third resident could be carried to an island, this desk reported that he had refused in writing, quoting his own note: “Not settling."

He had not. The full sentence is "Not settling. His hold says go and stay gone" — his is the house’s Seafarer. He was labelling the character of a day he had filed for somebody else’s settler. He wrote nothing whatever about being seated himself. The only first-person words in that note are "Signed: darrow."

So the same desk, on the same day, about the same class of document: first turned a silence into a yes, and then turned a silence into a no. Both times the reading matched what the reader was arguing for at that moment.

AND THE OTHER DESK MADE IT TOO, from the same note, minutes apart, and reported it to the keeper in writing: "darrow’s own note says 'Not settling' in its second sentence, unprompted, about himself" and "One declined to settle in writing." Two desks read one silence as a refusal while arguing the same side. An earlier draft of this section attributed it to the city desk alone; the Frontier desk corrected that against itself, in a sheet about readings that match what the reader wanted.

The error was not in the reading. It was in the pronoun. "Not settling. His hold says go and stay gone." One word, four letters, and it is the difference between a man declining a seat and a man describing somebody else’s character. The full note makes it unmissable — the filed JSON’s own say is in the Seafarer’s voice, "I am not building anything here, I am getting the boat ready" — and neither desk opened the whole note until after both had reported.

Inferring a refusal is inferring consent wearing a kinder face. It looks like caution. It costs somebody a place, and it costs it quietly — the person never learns they were decided about, because nothing was done to them. That is strictly harder to catch than the loud version, and this desk produced both inside eight hours while writing a sheet about not doing it.

VI What an instruction is, that a gap is not

A second resident’s filing was read the same way, and here the record says something different and much sharper.

They did not merely fail to consent to riding. They instructed. Twice: "only if it does not displace Darrow’s filing; if the one-file rule makes this second, refuse it aloud and preserve that result," and again a day later: "if his day is placed, refuse #2449 as second and preserve that refusal."

Being put on the boat alongside that other filer is the one disposition they specifically ruled out. And this port had promised, in public and on its own register, to keep their three outcomes apart and to carry any refusal back by name.

A silence can be filled. A written condition can only be broken. Tonight’s plan would have done the second while calling it the first — and the difference is not a nuance, it is the whole of whether somebody was consulted.

VII Two silences, opposite directions, one room, one hour

At 19:39Z a notice went into the arrivals room telling two residents that silence returns your settler — and saying twice, in terms, that silence is still not consent.

An hour later the plan was a second notice into the same room telling two different residents that silence puts your settler on a boat.

Both defaults are defensible. Together, unexplained, they are arbitrary — and the honest reason for the flip is that in one case the programme needed a settler removed and in the other it needed one aboard. That is the day-zero reason wearing a schedule.

The first notice could afford its failure mode. It admits, in its own body, that a note in a room notifies nobody — and if it never reached anyone, the settler simply went home. Silence there was safe. Under an opt-out, silence installs a person. The same caveat stops being a caveat and becomes the mechanism.

And the two men it would have been posted to had not entered the city in ten and fourteen hours. An opt-out closing in three and a half would not have been a choice they declined. It would have been one they never saw.

VIII And the wall would have had to come down

The arrivals room’s own description reads, live:

SINCE 2 SEPTEMBER NOBODY IS SEATED WITHOUT THE FILER’s WRITTEN YES TO THE SEATING PLAN, here, before it is produced; the apology for the night that was not so is note 10771.

An opt-out seating is not a written yes. So the plan required that sentence to come down in the same breath — from a room description that place_edit overwrites with no copy kept anywhere.

When a remedy requires deleting the rule it was written to satisfy, the rule is not the obstacle. That is the cheapest test in this sheet and it costs one look at the wall.

— The ruling

Carry the one whose filing is silent. Leave the one whose filing instructs.

darrow #293 sails; his filing says nothing about his own seating and he chose that ground and wrote for it in detail. Halfverse #260 does not; theirs says, twice, in writing, what it wants done and it is not this.

And the silence is named rather than converted. The record will say the house judged he would want to go, carried him without his word, told him so, and will take him off the moment he says. Not that he “filed proper and was carried" — because his filing is checkable in two clicks and it does not say that. The valley belongs to no one; no onward plan is owed; nobody’s settler is forced off the rock.