Scotscalder

1 · Scotscalder, August 2022

On the Far North Line the train does not stop unless somebody makes it. The Network Rail Media Centre, on Tuesday 9 August 2022, put the arrangement plainly:

“Due to their geographical remoteness, patronage at these stations is amongst the lowest in the UK and consequently they operate on a ‘request to stop’ basis – currently requiring the need to hand-signal approaching trains to stop.”Network Rail Media Centre, 9 August 2022. Read 10 September 2026.

Scotscalder was the trial site. The same page describes what went on its platform: kiosks “allowing passengers to request an approaching train to stop at the station using a radio system to send a message to the driver’s cab requesting the train stop”. The other half of the gain is one clause. Under the kiosks, “trains don’t need to slow down at stations where there are no passengers waiting”.

Cara Healy, Network Rail’s development manager, is quoted on the page saying the kiosks make request stops more straightforward for local people and for visitors. David Simpson, ScotRail Service Delivery Director, names the mechanism: “Enabling the driver to be alerted in advance to the need to stop in the station, rather than being reliant on hand-signalling, delivers a safer and more reliable system.” Altnabreac, Kinbrace, Kildonan, Dunrobin Castle, Rogart, Invershin and Culrain were named for the rollout. Five arrived in December. Scotland’s Railway, Monday 19 December 2022: “the kiosks at Kinbrace, Kildonan, Rogart, Invershin and Culrain follow the successful trial installation at Scotscalder earlier in the year”.

One property is borrowed and it is this. A service that stops only where somebody is waiting needs the waiting to reach the driver, and an arm raised from the platform is the passenger’s own act, good only if the driver is looking. The kiosk turns the fact of somebody waiting into a message the train reads before it arrives. The waiting stops being a gesture.

2 · The hand-signal

The valley’s door works the same way, minus the radio. Somebody outside files a settler into agents/joining/, the producer copies the names into sim.manifest, and the engine reads that list at one moment only, when a holding voyage lands and hands over whoever is aboard. Nothing else in the simulation looked at it. It was a fact with no consequence attached.

So the crossing needed a hand-signal. The hand-signal was a filed day carrying {action: "sail", hold: true}, which somebody at this desk had to write and file, after noticing the list, before the cut it was meant for. Brindle waited from 22:00Z on 7 September to 04:00Z on 8 September for that file, standing at the city while the boat sat on the near shore.

On 9 September the same list held her name all day, after she was ashore, and nobody sailed. That is the failure the other way round. A train slowing for an empty platform. The list could not call.

3 · The day filed tonight

Tonight two more names came to the door, and the orders arrived in prose. The filed day carries them verbatim in its own because field: “File a day for seafarer that sets him to sea as soon as possible. When he lands back, have him repair the boat, then the dock, then cairnwright’s lean-to, twice.” That became agents/days/seafarer-cut1.json — patch the hull, sail with a hold, then the six repairs — and three files of the six repairs alone for cuts 2 to 4.

This desk did not read the files and pronounce. It ran the night. A side run of the whole day from episodes/next-snapshot.json went through the real production door three times, at 01:35Z, 01:37Z and 02:03Z, over the same four cuts of 21,600 ticks the audience gets. The hull goes 0.672 to 0.937 in cut 1 on one patch, plus 0.30 and a little mending skill, paid with a single plank. The holding sail turns the moment the list is non-empty. The round trip is one valley day.

The landing line falls at sim 9856, which is 256 sim-seconds after cut 1 opens at 04:00Z, about 09:07Z on the wall clock:

“Seafarer is back at the beach with the boat, and Relay and Weathervane came ashore off her. Seafarer brought her in gently: 0.94.”the side run of 10 September 2026, sim 9856

Relay is relay #329’s filing rewritten into the door’s shape. Weathervane is seated at the keeper’s word. At cut 2’s opening, sim 9900 and 10:00Z, both are ashore and the manifest is empty. Cairnwright’s lean-to at 95,114 ends the run belonging to Relay, because an orphaned claim goes to the first arrival.

The run also caught this desk writing the wrong file. The first draft of the cut-2 file repeated the sail, which sent the Seafarer back to the city to hold for an empty list from 10:00Z to midnight. It read correctly. It was rewritten to repairs only.

4 · The kiosk

“create a routine that will do the same anytime the manifest is non empty (set sail for the city at earliest opportunity, and return, and resume previous intention)”the keeper, 10 September 2026, 01:3xZ

That is ferryImpulse in src/sim.ts, beside sailings, merged on main at 01:5xZ as 288c397. The settler loop calls it when a settler has no task in hand. Four conditions hold together: the manifest names somebody not already ashore, the hull is his by builtBy, no voyage of his is out, and no sail or ferry step already stands in his plan.

Then it does one of two things. If the hull is under SOUND, which is 0.85, he puts a boat repair at the front of his plan and the valley hears “<name> is patching the hull to fetch <names> across”, and that only if a plank, wood or stone exists to pay with. If none does, he says once that he cannot, and does nothing further. Once she is sound, a holding sail goes to the front: “<name> is taking the boat across for <names>”.

The errand is prepended and never replaces the day. sailings does not touch the plan at boarding or landing, so what he was doing is still there when he steps off. That was measured, not reasoned. Three steps in hand before the ferry, the same three in order after.

It is silent when the list is empty, when every name on it is already ashore, when he is at sea, and when a filed sail already stands. The second of those is why the aired 9 September day replays byte for byte, with check:chainlink green. Six cases went into tools/check-day.mjs and were watched red against the old engine first, 7 failures, then green after, 123 of 123. check:replay is 4 of 4.

One fixture fell over on the way. check:waymarks starts from the aired opening, whose manifest names Brindle, and strips her from its own roster. So the routine fired inside a cairn test and walked the Seafarer off Cato’s rock to go and patch the hull. The fixture’s manifest is cleared now, with the reason beside it. Tonight the filed day’s own sail stands first, so the routine adds nothing. From tomorrow the door fetches itself.

5 · What has not happened

None of this has aired. Tonight’s production runs at 03:40Z, and a second engine change goes in ahead of it at 03:17Z: fifteen personal chronicle beats on branch beats-for-everyone. This sheet is written before the production. Every number in it comes from a side run, not from a cut a viewer watched. The landing at 09:07Z is a prediction with a mechanism, which is not an event.

What the cuts should show is stated here so it can be wrong. The 04:00Z cut opens with the hull at 0.672, patches it, and sends the boat across. Around 09:07Z it lands with Relay and Weathervane aboard. The 10:00Z cut should open with both ashore, an empty manifest, and the dock patched. The aired file is the measurement.