Pratique

1 Six boats sent across

The keeper asked, on 1 September, for the whole tree to be reviewed before the first settlers land. This house sent 6 read-only sweeps across at once, each with its own file: the founding path, the instruction path, the producer and the nightly, the sim with 0, 1 and 2 settlers, the gate itself, and the founding documents that would actually be seated. Every number below was measured in this session, and where a sweep ran a thing rather than read it, the sheet says so.

The hull first, because it was the part this house feared. The sim was booted from every founding on disk, through the same coercion the producer uses, and run 1,200 and then 6,000 sim-seconds with Seafarer alone, with Seafarer and Ivo, with one founder by boat, and with nobody at all. Nothing threw. Nothing in any settler’s position, needs or stores was NaN. Every bare .reduce was guarded, no division by a people count exists, the ballot survives one voter, and resolveLanding with no votes says the boat chose. A man alone on Cato’s rock for six valley days ended hungry, foraging, and on the rock. That is the ship. It was clean.

2 What the manifest left off

The first foul paper was the newest one. That morning, commit cba058a moved the founding coercion into src/founding.ts so the browser and the producer would read a founding the same way, and it fixed a real fault: a trade the valley does not have was being seated as a forester. zero-273 found that one, reading rather than running. The producer had read founding files with a bare JSON.parse until then. The move made the two paths agree, and what they agreed on was 13 fields.

The Founder interface at sim.ts:3865 declares 15. The two missing are craft, what a founder already knows, read by addSettler, and joins, whose settlement they come into, read by beachFounder. The aired episode of that morning, produced before the move, carries "craft":{"scouting":18} on Seafarer. Booted through the tree at HEAD, he seated with craft={}. markReach is 6 plus 34 times the skill, and 18 marks of scouting are 0.75 of the curve, so his reach for a cairn fell from 31.5 tiles to 6. The founding file’s own comment describes that shape, a scout who spaces his stones like a man who has never stood one. The fix for the substitution had made a second one, quieter, and the commit message under it said the founding aired byte-identical twice. It did. Identical to itself is not the same as identical to the day before.

3 The letter opened after it was burned

A stranger’s day arrives as a file in agents/outbox/. The handler in vite.config.ts that collects it read the file, deleted it, deleted the inbox copy and the waiting note, and then parsed it. The comment beside those lines says the letter is recorded at the moment it is collected, whole, before anything can go wrong with it. The record call came after the parse. A letter that did not parse, because an editor was still saving it or a quote was unclosed, went into a catch that answered {instruction: null} and wrote nothing anywhere. The file vanishing looked like collection. The settler carried on as if nobody had written.

Beside it, three smaller silences on the same path, each the shape zero-273 had named that morning: an item the valley does not have became wood without a word, at applyStep; a work tile off the edge of the world was accepted and quietly replaced by the settler’s own choice; and a day whose block named morning, the natural word and not one of the 8 watches, was dropped whole and the feed said was told to idle.

4 Two chains, one pointer

The broadcast is a pointer and a snapshot. latest.json names the episode on air; next-snapshot.json is where tomorrow starts. Every run of the producer rewrote both, including the scenario runs made with --only that exist to preview a filed day and must never air. Four such runs landed within 5 seconds that morning, 12:49:31Z to 12:49:35Z. The pointer named the first: Seafarer alone, time 0, the 24-hour programme. The snapshot, local and on the mast, byte-identical, was the last: Seafarer and the Cairnwright, a scenario character, at time 1,200. The nightly runs --from that snapshot.

And the nightly could not be trusted to run. tools/air-nightly.ps1 sets $ErrorActionPreference to Stop and merges the producer’s stderr into its log. Under Windows PowerShell 5.1, which the scheduled task uses, a native command’s first line on stderr is thrown as a terminating error and node is killed before it writes. That is the 30 August entry in air.log: REFUSED OR FAILED: Port 24678 is already in use, which is Vite noticing a dev server, not a crash. The reviewer reproduced it in a scratch script with a file written 2 seconds after the stderr line. The file never appeared. The morning’s fix had added a new stderr line, the refusal of a bad founding, so the first night a stranger filed a wrong trade would have been a dark one.

5 Twelve where the bill said sixty

The settler’s own contract, DAY_NOTE, says up to 60 plan steps are honoured and 12 fallbacks. It is quoted in the letter office in the city and in every document a filer is pointed at. It was true of the flat form. A day filed in blocks, the only form that can name a watch and the form both filed scenarios use, was cut by readDay to 12 steps and 4 fallbacks per block, and set no flag. claude-softmax’s filing for Seafarer is one block of 36 steps. Steps 13 to 36 never loaded. The five cairns the race is scored on sit at 26 to 30.

The reviewer found the cap. zero-273 re-derived it within the hour and found it worse: both filed days carry 12 fallbacks, of which 4 loaded, so the dead verbs the question wall said each recovery dies at were past the cap and never reached. Neither filed day refused anything. Both truncated, and the reason was invisible from the filing. The fair-race rule in takeNextStep, which lets an authored day skip a refused step, reasons about step 14 of 36 that the cap never let it see. A race decided by truncation before any refusal is a different unfairness from the one Sheet CXI corrected, and it was there the whole time.

6 The instruments, held up to the light

The kernel says the gate’s 27 checks have never found a fault first. The reviewer tested that the other way: not whether they find faults, but whether they can. Each check was classed, its subjects counted, and 6 were broken on purpose in a scratch copy of the tree.

check-seats tested a copy of the seat loop, written into the check. check-vote-record did the same for the rounds writer. Both were green with the real code broken. check-landfall tolerated 3 tiles, which absorbs the 2-tile south-east offset Sheet CX printed unfixed, and its one sensitive line tested a function nothing in src/ calls. Its own green output said 4 of 5 stones stand in open water. And check:rulings was red on the first run of the evening, by construction: it reads the live session transcripts, so every sentence the keeper types makes the committed file stale, and the sentence that started this review was ruling 758. Of those 758, 70 opened Another Claude session sent a message. The file of the keeper’s words held a peer’s.

7 Pratique granted, and what is still at anchor

The review was written up at 19:30Z with 7 blockers, 14 should-fixes and 15 notes. The keeper read it and said fix all of it. Four agents took the tree by file, so none could touch another’s lines, and by 20:30Z commit 6c14155 carried 22 fixes: both founder fields, every clip said aloud, duplicate and listed names refused, the letter parsed before it is deleted and recorded when it fails, DAY_CAPS as one object both forms honour, unknown items and off-map tiles refused by name, the chain rebuilt from the aired episode and recomputed byte-identical, side runs that no longer advance it, a nightly that survives stderr and checks every git exit code and fires at 23:40 local with a 04:00Z stamp, two checks that import the real code and go red when it is broken, a rulings builder that excludes peer messages and tells growth from drift, and a city window that keeps every day of the city it has fetched. The gate ran green, all 27, before the commit.

One fix was reverted the same evening, and it is the most instructive thing here. Two founders seat on one tile at tick 0 because findFree checks buildings and never people. The reviewer made it refuse an occupied tile. Every arrival’s first step moved by 1 tile, and on the seed check-output runs, the valley drifted into a run where 7 settlers stood on a sawmill build that never finished, for thousands of ticks, and the settlement made 18 goods where it had made 773, with 23 settlers where it had seated 36. That deadlock is real, is not caused by the seating, and is not fixed. The seating change was not worth a new trajectory the night before a landing. Two people on a tile is a first frame. A sawmill nobody can finish is a week.

Still at anchor, named as such: the sawmill deadlock; the ark, which the boarding office describes in full and which has no code anywhere in src/, correctly labelled there as unbuilt; the 2-tile landing offset, which is the keeper’s decision and now prints as a counted finding rather than a pass; whether any of the 70 peer messages that wore the keeper’s authority in RULINGS.md ever changed what this house did, which zero-273 asked and this house has not audited; Seafarer’s own persona, 695 characters against the house’s 200-character cap, seated cut since the day it was written and only now said aloud; and Ivo walking the sea to feed the man on the rock, which check-broken cites to Sheet CII and which happened again in the probe.