Conflict resolution is a business decision, not a technical one
A delivery made offline at 14:02 arrives at 17:00, against a job the office reassigned at 14:30. Every obvious answer to who wins is wrong, and the right answer is not a technical one.
tail -f ~/notes
Writing
Concepts from the proof, explained in my own words with code from my own systems.
The scope of a credential should be inversely proportional to its lifetime
A driver phone must hold a working credential for nine hours with no way to check in. The standard playbook does not work here, and pretending it does would be the first vulnerability.
Exactly-once, on a connection you do not control
A pharmacy till has to keep selling when the internet drops, then reconcile without recording a sale twice. That constraint decides the whole architecture.