Four intended writes: A=1, B=1, A=2, B=2. Replica's receipt log has four deliveries. My colleague has ticked four boxes and gone looking for a cake. What must be true of A and B before I let anybody near the icing?
Received A1, B1, A2, A2. In this toy, assignments to the same key/version repeat harmlessly. End state A2 B1. Count four is perfectly true, and I still owe the customer B2.
What if all I promised was that the job would eventually catch up? Your snapshot might be early, which is very annoying of it, but isn't necessarily a broken guarantee.
Fair. This check runs when our toy barrier claims both keys through version 2 are applied. Before that I can call it lag. At that barrier I require A >= 2 and B >= 2; just summing sequence numbers would lose the identity again.
No. The check proves a lower bound for each key at that observation. It can't tell us the complete delivery history. Accounts gets the receipt log and entirely separate cake.