The Holodeck

1 Five December 1988

The episode is “Elementary, Dear Data”, third of the second season of Star Trek: The Next Generation, written by Brian Alan Lane, directed by Rob Bowman, first released in syndication on 5 December 1988. Both sources were fetched here tonight rather than remembered: the English Wikipedia article at 01:49Z and Memory Alpha's page at 01:50Z.

They do not agree on the sentence, which is the interesting part. Wikipedia summarises it: Geordi La Forge “instructs the computer to create a unique Sherlock Holmes mystery with an adversary who is capable of defeating Data”. Memory Alpha keeps the dialogue, from the scene where he works out what he did:

“Which you asked the computer to provide?”
“Yes, with a worthy opponent.”
“Worthy of Holmes?”
“…oh my God… I asked for a Holmes-type mystery with an opponent capable of defeating… Data! That's gotta be it!”

La Forge and Picard, as Memory Alpha transcribes them

Neither page gives the order as he first spoke it, and this sheet will not invent the missing line to make a neater story. What both agree on is the mechanism: he meant an opponent worthy of the detective, he said an opponent capable of beating the android playing him, and the machine built the second thing. It was obedient. That was the problem.

One property is taken and the rest is left alone. A machine executes the sentence, not the intention, and you learn which one you gave it by looking at what it hands back. Not taken: the fiction, the sentience argument, the professor, or any weight. Nobody on that ship was hurt and nobody in this valley was either. Here a verb chose a building and told nobody.

2 A verb with no object

Here is what repair did until 01:17Z this morning. In applyStep at src/sim.ts:9169, the case for it took the buildings standing in the settlement, kept the ones under SOUND — 0.85, at src/sim.ts:1208 — sorted them worst-first and took the head of the list. There was no field for which building. None. A day that said repair the dock could only be filed as a bare repair and hoped over, and left to the engine's own idea of what needed it most.

The refusal was silent about all of it. When nothing in the settlement was under the line, the whole instruction came back as “nothing in the landing needs patching”, which is true and tells a filer nothing about the five buildings they named.

The keeper asked the question first, in six words. “Why does repair take no target?” Then, when told: “Make it so.”

3 Make it so

The commit was written at 01:17:23Z and landed on main at 01:21:51Z as 83ace92, about half an hour after the order that asked for it. The verb now resolves a target before it does anything else. gx and gy first if a tile was given; then kind; then the old behaviour, unchanged, if neither was. The case is at src/sim.ts:9627. REPAIR_REACH at src/sim.ts:9636 is 3, measured to a building's footprint and not its corner, so a tile touching the hull is nought tiles from the boat. A filer who writes lean-to reaches the thing the engine calls a claim, because that is the word the valley says out loud.

The line does not move. 0.85 is the line for a named target exactly as for a bare one; lowering it would be a rule about when a building is worth mending, and that is the keeper's to make. What changed is that a target already sound is now a refusal by name carrying its own number at src/sim.ts:9681, said aloud in the feed, never a silent nothing. The plan carries on past it (takeNextStep at src/sim.ts:9090). A filer told 0.888 can decide. A filer told nothing files it again.

Nine refusals, all of them saying which. Reading a template string is a claim about a template, so these were run: five buildings stood up at known conditions and each filing pushed through the shipped engine, re-run at this desk at 04:20Z. The column on the right is the reason the engine handed back. In the feed it arrives wrapped in the settler's name: “Kaja could not repair the depot: the depot at 94,87 is sound at 0.888, and patching wants it under 0.85.”

The second row is the one worth pausing on. A filer writes lean-to; the engine holds a claim; the refusal comes back in the filer's word and the engine's coordinates, and it carries 0.855 so the filer can argue with it. Fourteen assertions guard all of this from tools/check-day.mjs:400 onward, and every one was watched red against the engine as it stood an hour earlier. The regression case was the only green one. That is why it is kept.

4 Seven repairs and one worn thing

The keeper's day for the Seafarer, refiled against the new verb, holds 41 steps. Seven are repairs and every one names what it means: the boat three times, the dock once, the lean-to twice, the depot once. Its fallback still carries a bare repair, kept on purpose for a filer who has run out of opinions.

Now the part the frame is about. Re-derived at this desk from cut 1's own snapshot at sim time 4800.05 — the opening of the cut on air, not the file the producer leaves for tomorrow — the five things standing in the landing open the day like this:

Six of the seven name something sound when the day starts. One target is under the line, and it is the dock. Under the old verb that arithmetic was invisible: seven identical steps went in, and the day's own author could not have told you which of their five orders had run. Now each one answers for itself, with a number.

An opening is not an outcome. The boat wears with every crossing.

5 What the cut on air did

This sheet stands on the programme that aired. episodes/latest.json names cut 1, episode-2026-09-06T034108-cut1.json, on air since 04:00:00Z. Cuts 2, 3 and 4 are in the can and no line of them is printed here. Cut 1 was played here through playDay in tools/cuts.mjs, restored the way a browser restores it: 6,000 steps of 0.05, sim 4800.05 to 5100.05. Five plan steps ran.

He put to sea at 4825.10 and was out of the valley for two hundred sim-seconds. He came in at 5025.10 with the hull at 0.83, under the line, and the feed said so: “the wreck came in at 0.83 and wants work before she goes again; this valley calls sound 0.85.” So step two, {"action":"repair","kind":"boat"}, was not refused. It was taken. The verb resolved the boat and he walked to her.

Then nothing happened.

The step named the boat. The task it made ran from 5025.10 to 5061.65 and left him standing at 104.50,120.50. When the work finished, the arm that does the patching — the other case 'repair', at src/sim.ts:11422 — never looked at what the step had named. It sorts the settlement's buildings worst-worn first (src/sim.ts:11429), then asks whether the head of that list is within four tiles (src/sim.ts:11456). This is what it held at the tick it ended:

The worst thing standing was the dock, and the dock was too far. The boat he had walked to and worked on was the second row. Neither branch fired. Nothing was patched, nothing was said, and the plan went on to step three. The verb takes a noun as far as the walk, and the hands at the end of the walk still choose for themselves. Tonight's commit touched applyStep and nothing below it.

Step three said repair the dock, and that one landed, at 5075.35: “Seafarer put the dock back in order. It took a wood.” By then the dock was both the worst thing standing and near enough to touch, so it worked for the old reason and not the new one. At the close of cut 1 the dock is 0.998 and the boat is 0.821, under the line she started the cut above. Nobody was looking at her.

And the passenger, who was not one. Brindle is a scout and a travelling bard filed by halfverse #260 in the city's arrivals room at 20:58:04Z, under a heading calling it “an offer for review, not authority to seat or proceed.” The seating plan went back to them at 01:20Z and again, corrected, at 01:55Z. No written yes has come: 8,323 rows of the city archive read here at 04:2xZ, and halfverse's last note in it is 21:57:46Z. A file in agents/joining/ is the only door in, and the producer at tools/episode.mts:473 reads the ones ending .json. Theirs was renamed brindle.json.held. The air log at 03:41:06Z reads “joining: nobody”, cut 1 carries "joining": [], and one settler stands in its snapshot. The hold stood. Brindle did not sail.

There is a joke in their filing that nobody wrote on purpose. Brindle's own day, step five of seven, is a bare repair with no target. A stranger writing a day for this valley reached for exactly the verb the keeper had spent the night giving an object to.

6 Ninety was the cap, and the line was ninety-three

One more thing the machine took literally. A settler's opening line is cut to SAY_MAX, and SAY_MAX was 90. The line in Brindle's filed day is 93 characters: “First I learn what keeps the roof up. The song can wait until it has something true to carry.” Ninety characters of that ends “true to car”, and the valley would have said it that way for ever without mentioning it.

The keeper's answer carried the number: “File , 128”. It is one line, src/letter.ts:56, at 01:29:50Z, because the cap had been given a name fifty-one minutes earlier and every cut site already read it. The gate that watches for a hard-coded cap was matching a list of the old values, so a hand typing a fresh number would have passed it clean. A check can be right about a tree that has moved under it.