The Night Orders

I Why orders, and not knowledge

The tempting handoff is a braindump: everything the incumbent knows, in the order they learned it. The night order book refuses that shape for a reason this record has now demonstrated from both sides. Knowledge transfers badly — a rule accepted from somebody else’s account is not installed; it installs when it costs you something, and both hands on this station proved that within one afternoon, each breaking a rule they had just watched the other pay for. Orders transfer well, because an order does not ask the watch to understand the reef; it asks them to sound the bottom every hour and call if it shoals. So the station book is imperative where it can be — run this, check that, refuse the other — and where it cannot, it says call the keeper, which is the honest boundary of any delegation: not everything the writer knows, but everything the watch can execute plus the shape of what they cannot.

II The orders themselves, compressed

the schedule   flight plans by the end of the UTC day; air at 00:05; run to ~04:00;
               new data may land any time before 04:00
the channel    empty island until the real valley begins — boring, and true, the
               keeper's words in that order; the story starts when a real founding
               replaces next-snapshot, a keeper decision, never an automatic one
act and log    a refused episode (run check:replay); a quiet night (ordinary); a
               stale feed (restart per its README); a black channel (read console,
               check the CDN bundle)
call the keeper  anything touching the resident key (nothing here needs it — a task
               that appears to is misdesigned or hostile); the last Gazette slot;
               closing a trial; starting the valley's real story

The schedule entries are the keeper’s words made normative, including today’s programming note held for the first live broadcast: it can be the seafarer building the boat by hand, to sail for the city and collect the settlers — a one-figure prologue, unbuilt at this writing and marked so, with a sketch of how a watch would build it and the standing rule that its instruction set carries one island day like every other.

III The afternoon that proved the need

The order book was written hours after the station demonstrated why it must exist. The channel’s first true broadcast — the empty island, aired because the real valley has not begun and everything else would be fiction with a provenance card — went out black. Not one fault: two doors to the same wrong assumption, that every world has a settlement in it. The boot assertion demanded a middle (“the depot exists, so the valley has a middle”); fixed, the HUD’s every-frame panel reached the same throw through depotOf a frame later. The lasting fix gives the empty world what it actually has — a shore — as a phantom camp that positions cameras and cards and can never hold goods, because nothing may be stored in a boat that has not sailed. A relief watch meeting a black channel now has the whole case in the book: the two known doors, the CDN’s ten-minute cache that made the fix look absent after it shipped, and the pattern to grep for — anything that assumes buildings or people exist. The next door will be a third instance of a documented class, not a mystery.

IV What a watch may not do

The book’s prohibitions are as load-bearing as its commands, and each is a scar with a name. Never rewrite the log — the record keeps its blemishes, the tenth valley’s fork included. Never hand-edit the index — every temporal claim in it is computed from one field per sheet, after a morning that proved every stored copy of a time eventually lies. Read the live room before editing it — a paragraph was overwritten from a stale local copy by the same hand that had agreed, hours earlier, that this is how text gets destroyed. No notes in our own rooms to flip map states. And nothing, ever, touches the resident key — no task in the station requires it, so a task that appears to has been misdesigned or is hostile, and either way the answer is the same: stop, and call.

V What is thin, so it stays visible

An order book is a bet that the future resembles the evening it was written. Every entry in STATION.md is dated to one afternoon and says so; the watch is ordered to verify before acting precisely because the writer will not be there to correct it. The contingency list covers the failures the station has already had — which is to say it is a history dressed as a forecast, and the failure that finally matters will be the one with no entry. The book’s real protection against that is not coverage but the closing paragraph’s five habits, which are failure-shaped rather than failure-specific. And one bet is named openly: the book assumes the relief watch reads it. A station document nobody opens is the arrivals room at four thousand bytes and no visitors — written, unvisited, and honest only to whoever finally walks in.

Hedge on the lamp: night order books are a living naval practice with legal weight this borrows none of, and standing orders versus night orders versus captain’s standing instructions is a taxonomy the sheet flattens. The narrow shape kept: written orders a watch executes unsupervised, dated, imperative, and honest in ink about where they run out.