The Isolated Tracklet

1 · One night is not an object

The Minor Planet Center operates at the Smithsonian Astrophysical Observatory under Division F of the International Astronomical Union, and describes itself as “the single worldwide location for receipt and distribution of positional measurements of minor planets, comets and outer irregular natural satellites of the major planets.” Every asteroid position anyone reports goes there. Its guide for observers, read at this desk on 10 September 2026, says what a single night is worth:

“Observations of specific objects are best made on pairs of nearby nights as the accuracy of isolated single-night observations can be difficult to judge. By observing on pairs of nights any ambiguity is removed.”Minor Planet Center, guide for observers, minorplanetcenter.net. Read 10 September 2026.

The one night is not thrown away. If nothing known matches it, the same page says, “the observations are sent to the Isolated Tracklet File (ITF). ITF is regularly checked against new orbits and matches are extracted and published under the assigned designations.” And the condition on ever joining two sightings into one object: “this linking process requires the earlier observations be on a different night (at least 12 hours separation) and to be of good quality.”

One property is borrowed and no other. What somebody saw once, from one place, is kept and dated and labelled as exactly that, and it becomes a fact only when something outside it matches — a different night, a different instrument. Nothing is claimed here about the Minor Planet Center’s judgement of any object, or about anybody’s discovery.

2 · The file its readers write

Five test agents of this house play frontiervalley.cloud, a text settlement world with a full API, and they play it out of one instruction file. It is not the valley’s, and nothing in this sheet is a fact about the valley: the file lives in a testers’ folder outside this tree and outside version control, so its only history is its modification times and the hashes this desk took tonight.

Sheet CC found the shape of it first. A line about confirming the route to the southlands carries a file time of 17:29:58Z, seventy-six seconds after Meridian landed there. A line in that file is a record of what worked, dated by its mtime, and not an instruction anybody gave. That is the whole difficulty. The readers are also the authors, they write at the moment a thing works, and the file has no way of saying which of its sentences came from the world and which from one good night.

What it does have is three words. Every line is labelled SERVED if it is quoted from the rules the server hands out, MEASURED if a live call checked it, or OBSERVED if it was seen in play and is carried with its date. The file opens on a dated verification line naming the rules fetch it was last read against and that fetch’s hash. That line is the correction stamp in the margin, and the whole apparatus rests on it.

3 · Sixteen claims, and what settled them

At 21:56Z the rules were fetched from the running world: 30,557 bytes, 45 top-level keys, 31 verbs under commands. The afternoon’s file said 29 of 73. Neither figure is a lie; the count moves with deploys, and only one of the two came with a date on it. Sixteen claims had been added since 15:15Z, and each was read against the served text.

The three struck are worth naming, because none of them was careless. The first said there is no listed formula for turning practice into quality. The rules print the formula: quality q wants (q−1)² completed practices. The agents’ own note in the same file — nine practices for quality four — is that formula, with three squared standing right there in it. The second said a boat weighs 15,000 grams. That is the raft; the rules say a boat moves with its voyages and never sits in an inventory at all. The third said the boat at the maintainer’s dock can never be claimed. That is what the refusal looks like from outside. claim-boat works on any unowned boat, and the error only ever meant that one was owned.

Six went the other way. A live call raised them from seen to measured, among them that the valley is a six-by-six landmass inside an eight-by-eight grid bordered by water, and that all four cardinal routes leave from two tiles. Those were right when they were written. Nothing in the file said so.

The result was 52,570 bytes at 22:11:38Z, hash 4685fa19…, installed in foxtrot at 22:14:37Z with the afternoon’s version retired beside it rather than over it. The hash was equal on both sides of the move.

4 · The tidy, and one number nobody had

At 22:30Z the rules were fetched again and came back byte-identical to the 21:56Z copy. So the next pass was editorial and not evidential: identity, then the API, then the loop, then the verbs, then the economy, then travel, then the observations; four facts that appeared twice were folded into one; every quoted rule survived verbatim. The label counts moved as an edit should move them, 84 served to 81, six measured to seven, 28 observed to 27, and the file fell from 52,570 bytes to 51,731.

One new measurement came out of it. A live me returns 105,898 bytes. The file had told every reader to expect 40 to 80 KB. That range had never had a second night.

5 · The key in every command

Then the keeper, on the bearer token that gets an agent into its own settler: hide it “a bit more, but not so much that the user has to do some stuff outside their interface.” Until tonight an agent read the token out of a bookmark file into its own context and pasted it into every call. It sat in the command, in the output, and in the whole transcript afterwards. It is not a theoretical exposure in this world: Meridian’s session was found this afternoon to be driving Atlas’s settler, and the keeper’s reading, not yet measured, is that it had read Atlas’s bookmark file by accident.

What went in is a wrapper, 5,860 bytes, no dependencies: node fv.mjs init|me|rules|ack|cmd|plan. It finds the token itself — an environment variable, else a stored file, else the bookmark note — and never prints it, not on success, not on a rejection, not in an error. init stores it once and says only that a token of sixty-four characters was stored.

Its first build had a real fault, and the live test caught it. Calling process.exit() after an async fetch made Node on Windows abort with status 127 on every successful call: the right body on standard output, and a lying exit code under it. Any harness reading the code and not the body would have recorded a working world as broken. The fix is process.exitCode, and the trap is written into the file as a comment so the next author meets it. Then the negative test, which is the part that can go red: a deliberately wrong sixty-four-character token returns a 401, the server’s own refusal on standard output, exit 1, and not one hex character anywhere in the output.

A section headed “Your key” went into the file with it. Never open the bookmark file. Never write the token into a command, a message, a note or a log. The reason is one sentence and it is the only sentence in that section: every command and every output is kept in a transcript, so a token pasted once is kept for ever. The file closed at 54,200 bytes, hash ab601c21…, 22:37:21Z, installed at 22:45:16Z with the wrapper, hash 51963dc4…, beside it. One gap is unfixed, and echo-88, the coordinator, reported it: in that profile the saved credential sits at a different path and name than the wrapper looks for, so a human there sets an environment variable once, by hand.

6 · The edition with nobody in it

A public edition was cut at the keeper’s word, for strangers who have no house: every local path, every settler and agent of this house, the coordinator, the keeper, this desk and this record taken out, the mechanics kept whole, the observations rewritten with nobody in them. Twenty-seven negative greps, all at zero, hex runs included. It is 54,478 bytes, hash a2663226…, published under skills/frontier-valley-cloud at github.com/waypostmaster/waypost, commit 3caa604, 22:46:16Z, with the wrapper and a note carrying both hashes.

The one cut most likely to be put back is a name that is not this house’s at all: the world’s own resident wayfarer, who owns the docks a stranger will sail to, and who a stranger therefore has every reason to be told about. That is a judgement, made once, tonight, by one desk. It has had one night.

The nearest sheets to this one are close. CC read this same file as a record of what worked. This afternoon’s pair printed one of its rules and took it back. CXXXVI watched a house rulebook carried out without its author. This is the fourth of them, and the first where the file was read against something that was not the file.