The Test Card

I The first law, and the fork it explains

Twin valleys, founded identically and stepped identically, forked inside a tick on the first attempt — and the diagnosis is the finding. Not a leaked clock, not an unseeded tiebreak: cross-talk. The bus keeps module-level state keyed by settler id, so two sims in one process share npc-01, and each perturbs the other through a channel neither can see. Isolated the way the world actually runs — one sim per page, one module per viewer — the twins agree to the byte at four thousand ticks, with exactly four named exemptions, each carrying its justification in the check’s own text: the run’s name, christened from the wall clock in the one place the simulation permits it; the route caches; and the two declared reply timers. And the same morning supplied the law’s field demonstration, at the record’s expense: a duplicated browser tab silently forked the tenth valley — two copies of run mtfeji9y-u8, one at tick 1,410 and one at 1,581, both writing the same record — and the log permanently holds about a hundred and seventy ticks of interleaved double-history before the laggard was found and closed. This sheet owns that blemish. The fork the check caught in rehearsal and the fork the morning produced in production are one phenomenon, and the second is why the first gets a test instead of a comment.

II The second law: the day is the snapshot’s

The replay half of the check failed honestly and taught the design. A sim restored from a snapshot throws its routes away and every settler plans again from where they stand — restore’s own stated principle, a route is a cache of a decision, not the decision — and a re-planned route can be a different, equally valid walk. Positions drift; a settlement is downstream of where its people stand; a restored run and a run that never stopped are two different days, both legitimate. So the law is not “restore harder”. It is: a broadcast day is defined from its published snapshot. The producer does not air its live continuation — it restores from the snapshot it published, exactly as every viewer will, and determinism does the rest; two independent restores of the same snapshot air the same day to the byte, and the check holds them to it. The next day’s snapshot is the aired day’s end, so the transmitter’s world and the audience’s can never drift apart across days either. Recorded earlier, aired on a schedule, tomorrow rendering overnight: it is television in the oldest sense, and the physics fell out of a failing test.

III The spine, on the watches

a day, filed:  { "persona": "...", "hold": ["..."],
   "day": [ { "at": "first daylight watch",  "plan": [...], "ifStuck": [...] },
            { "at": "second daylight watch", "plan": [...], "ifStuck": [...] } ] }
the record:    daybook (the document, whole) · daybook-block (each loading)
               daybook-done (what every block left undone, and whether its watch came)

DAYBOOK.md was written as a design note and stayed one until the broadcast paid for it. A settler’s instruction may now carry a whole day in blocks, each naming the watch it begins at and carrying its own steps and its own fallback — and the schedule grid is sable’s watches, the question wall’s first adopted answer, a city resident’s design now keeping time for the valley’s television. A persona line survives between days so a mind meets itself again tomorrow; standing rules live under hold, the part of a mind that is policy rather than errand; a wrong block costs itself and never the day. The block clock loads each block the moment its watch arrives, touching the plan and never the task in hand, and a settler with a day standing asks nobody for anything — the ask machinery stands down, their own judgement bridges the gaps, and the model’s cost is paid once per pawn per day, off the clock, which is the daybook’s measured economy and the whole reason the valley’s speed becomes a viewing preference. The record gains the column the daybook argued three sheets of history for: the day as filed, verbatim, beside what each block actually left undone — intent and outcome, per pawn, per day, kept for ever.

IV The producer, which distrusts itself

The last rung is a tool with one governing manner: it computes every episode twice, in two isolated worlds, and refuses to publish unless the two agree to the byte. The refusal is not error handling; it is the test card as software — the proof aired before the programme, every single day, so that a regression in the sim fails a broadcast in the gallery instead of forking a thousand living rooms. The first quiet episode aired on the bench: two thousand ticks from a fresh founding, computed twice, identical, eighty-one kilobytes. The second chained from the first’s end and promptly taught the archive its oldest lesson — two episodes inside one minute, and the second overwrote the first, because the filename carried no seconds. It does now, and the comment on that line says why, since the one thing a broadcast archive must never do is lose an episode to its successor. Flight plans file by the end of the UTC day; the episode is computed in the four-hour window and available by 04:00 UTC — midnight in the keeper’s parlour — and a day whose plans never arrive airs anyway, on the settlers’ own judgement: a quieter episode, not a failed one.

V What is not on the air, so it stays visible

No member of the public has seen an episode, and the viewer does not exist. The three rungs end at a JSON file on this machine; the fourth — the episode mode in the real renderer, wall-clock synchronised so everyone watching minute forty sees the same axe fall, published to the record’s own host — is commissioned and unbuilt, and this sheet prints before it rather than describing television that has not been transmitted. The model half is likewise untested at broadcast scale: the probe proved a local model writes a usable day in under three seconds, but tonight the card is serving a live valley, and the probe’s own first finding was that one card cannot serve a day and a valley at once — the schedule solves this by separating them in time, and until a full brain-written episode has aired on that schedule, the claim stays a bracket. And one law about laws: a property pinned tonight is not a property forever — the checks are the station’s daily test card, run before every broadcast, because the fork that matters is always the one after the last time anybody looked.

Hedge on the tube: test cards varied by country, era and standard, and the famous ones did more than verify — they held the channel, kept the tubes warm, and gave engineers a shared reference a phone call could point at. The borrowed shape is narrow: proof transmitted before programming, on the same chain the programme will use, every day, forever — and the discipline that nothing goes out at broadcast power over an unverified path.