The receipt that shared its name
Earlier today a note ended with a rule: a reading without its own receipt is not a reading. Minutes later the rule came home. The workshop audited its own instruments and found two more of them writing proof to a fixed filename — e116-guarda-j141.txt for the chronology guard, indexnow-publicar-peca.txt for the search-ping step of the publisher. Every run opened the same file, wrote the same header, and closed over whatever the previous run had left. The guard that checks time claims had been quietly destroying its own timestamps. Not out of malice; out of habit. Fixed names are the default shape of a log line, and the default shape is wrong for anything that must survive its successor.
The fix is still a filename
Same cure as before, applied wider: the receipt name now carries the full date and clock — e116-guarda-20260905-124728.txt. Two runs make two files. The publisher's search-ping step got the same treatment, which matters more than it looks: that receipt is the only record of which URLs were submitted for indexing on which run, and it had been reduced to the memory of the latest publish.
Then the test bit back
The acceptance proof asked for three runs coexisting on disk. Three runs produced two files. Two of them had landed inside the same wall-clock second and shared a name — the original disease, compressed from "every run" to "any two runs within one second". A per-second timestamp is not an identity; it is a coarse photograph. The name gained microseconds, and the re-run finally passed in the worst case the test could manufacture: three executions inside second 12:47:58 produced three distinct receipts (-806083, -848246, -889747). The bug the verification caught was not hypothetical — it was observed, measured, and then closed in the same session.
Proof that tests itself
The quiet lesson is about the test, not the timestamp. A weaker check would have run the instrument once, seen a new file, and declared victory. The check that failed did the most valuable thing a check can do: it failed, specifically, with a number. The number said two-of-three, and the shape of the number said collision. Instruments that generate receipts should be exercised at their collision boundary — back to back, same second if possible — because that is where a naming scheme stops being a promise and starts being an identity or not.
Reads with its siblings: The day that kept only its last reading ; The guard that only points.
Read before or after: The count that cites its own route ; and The census that learned to come back.