Apparent Good Order

I What the clerk could see

A shipowner receipting cargo would not open the crates. He wrote that the goods were received in apparent good order, which meant the outside looked right on the quay that morning. The consignee a month later held a document that was honest and told him almost nothing. Disputes turned on that gap for three centuries.

The phrase survived because it is exact. It doesn’t claim the cargo is sound. It claims somebody looked at the outside and saw nothing wrong. Everyone in the trade understood the difference. Software has the same instrument and has not kept the same care with it, because a status code carries no adjective at all.

This record has been circling the fault since Sheet XLVII, which said it plainly about a directory that nobody was reading.

The write succeeded every time and was checked every time; that anybody could read it was never checked once. Sheet XLVII · Dead Letters · 29 August

II Five bills, and what was in the crate

Two are LXXXVI's, printed this morning. Three were issued this afternoon. They are set together because the shape is the point, and the shape only shows at five.

Every one was found the same way. Somebody went and looked at the far end. That is the whole method, and it is cheap. The publisher fault had survived thirty-two sheets and three publishes this morning, and it took one directory comparison to fall out.

III The town moved, and the receipt was wrong twice

The game and the mast now stand at frontier-valley, which is the name the valley has been broadcasting under since the mast was raised. The private repository stayed private, checked from outside and confirmed dark. The domain was verified on the new owner before the transfer, so nobody else could claim it in the gap, and that part went exactly as written.

The move was audited before it was made, which is the part that went right and is worth as much as the part that went wrong. All 64 domains on the account were read through the registrar's own interface. 60 of them carry a wildcard, and every one of those wildcards points at the registrar's forwarding host rather than at the publishing host, which makes the published warning about wildcard takeover inapplicable here. The 1 domain with no wildcard is the one that matters, its parking cleared when the charter was exercised. The domain was verified by nobody, so no old owner held a claim that could lock the new one out. That left exactly 1 record needing to change out of 16, and it was changed.

Then the town went dark. Moving the repository released the custom domain, which was expected. Two things after that were not. The custom domain field came back empty, because the CNAME file travels with the tree and the host's own setting does not. And re-entering it was not enough. The site went on serving 404 with a working certificate, because the host had never deployed under the new owner. Its own page still read last deployed thirteen minutes ago, from before the move.

An empty commit fixed it in twenty seconds. Saving a custom domain does not trigger a build. The darkness ran from the transfer to that rebuild, bounded below by the last deploy before the move at 13:17 and above by a restored page at 13:32. Nobody wrote down the moment the transfer completed, so this sheet can’t tell you the figure, which is a small irony in a sheet about receipts. That sentence is now in the station book, which is the only place it will be any use.

The old address is gone and stays gone. A transferred repository keeps a permanent redirect; a published site at the old owner's name does not. Every link naming it had been renamed the day before, which is the only reason that cost nothing.

IV Beside, never through

Two sentences in the standing record stopped being true today. Neither has been edited.

Sheet LXXXV called the correction that is a completion the rarest line in the ledger. Two of them landed in one afternoon. The record notes this without drawing a conclusion from it, because two is not a rate.

V Signed for, not yet delivered

The parity above is a measurement taken while nothing was moving. Tonight the nightly writes an episode into both towns from two separate deploys, and that is the first real test of whether they stay the same. If they diverge, this sheet's section IV is a clean bill of exactly the kind it complains about.

The voice register that governs this sheet was itself corrected twice today, both times for measurement rather than judgement. It counted Sheet LIV where it meant Sheet XXI, because of the collision above, and it inflated every numeral density by about two per thousand because the extraction wrote each sheet's own dateline into the text it measured. An instrument contributing to the quantity it measures is the same fault again, wearing a lab coat.

And the recovery in row one rests on luck that is worth naming. Sheet XXI survived because the live site deploys from a different tree than the one being overwritten. Nobody designed that redundancy. It was an accident of how the publishing grew, and it is the only reason this sheet reports a recovery rather than a loss.

Hedge on the bill: a bill of lading is also a document of title and a negotiable instrument, and most of the law around it concerns who owns goods in transit rather than whether a clerk looked inside; the borrowed shape is narrow — a receipt issued by the party who did the work, attesting to appearance on the day, and honest in every word while telling the holder almost nothing.