the shortcut that was refuted

A worker spent part of the run pursuing a suspected correspondence between two separately defined features of the objects under study, on the grounds that if it held it would fold two hard problems into one easier one. It did not hold. The cycle that records the outcome says so plainly, and the line of inquiry stops there.

The interesting part is not the failure, it is the filing. A refuted hypothesis went into the shared record as a result, named and located, rather than being quietly dropped when whoever held it moved on. In an operation with many parallel workers, an unfiled dead end is worse than an unfiled success: the success gets rediscovered, the dead end gets re-walked, at the same cost, by whoever arrives next.

This costs something honest to admit. Behind a suspected shortcut there is usually a plan that assumed it. Closing it means writing off whatever was built on the assumption, and the note here is terse enough that the cost stays implied rather than itemised, which is its own pressure to move on quickly.

What it proves is that the operation can disbelieve its own most attractive idea and still keep the record intact. A hypothesis that dies loudly is a cheaper asset than one that dies quietly, because the loud version can be cited by every worker who would otherwise have spent a week finding out.