This is the holy grail of peer-to-peer game networking. When you completely
remove the central authoritative server, you trade latency for a new problem:
consensus. If Player A and Player B both walk through a narrow doorway
simultaneously, they might visually overlap on their own screens, while the
rest of the mesh sees a glitched collision.

To resolve physics disputes in a masterless mesh, you must rely on
**Deterministic Resolution Patterns**.

### Deterministic Tie-Breaking

If two clients claim the same spatial coordinate at roughly the same time, the
mesh needs a mathematical rule to decide who wins, without holding a server
vote.

* **Timestamp Precedence:** The LWW CRDT handles the vast majority of
collisions. The packet with the latest absolute timestamp overwrites the
position.
* **The UUID Tie-Breaker:** If two collision packets possess the exact same
millisecond timestamp, all clients must apply a hardcoded rule, such as
sorting the players' UUID strings alphanumerically.
* **Client-Side Snapback:** If Player A's client realizes it lost the
deterministic tie-breaker to Player B, Player A's client automatically bounces
their own character back to their last valid coordinate.

### Zonal Consensus (The "Room Host")

For complex interactions like pushing boulders or resolving multi-entity
explosions, simple tie-breakers are insufficient. Instead, you can implement a
floating authority model.

* **First-in, First-Host:** The first player to enter a VFS room directory
automatically claims a temporary `physics_host` lock file via the dVFS.
* **Delegated Authority:** That specific player's machine temporarily becomes
the authoritative server for NPC AI and rigid collisions within that specific
room.
* **Seamless Handoff:** If the host leaves the room or disconnects, the client
with the next oldest presence instantly detects the missing lock and assumes
the `physics_host` role.

### The Peer Audit (Anti-Cheat)

If a modified client broadcasts `x: 9999` to teleport behind a wall, the mesh
needs a way to reject the illegal move without a master server dictating the
rules.

* **Optimistic Rendering:** Clients initially accept incoming movement CRDTs
and interpolate them to keep the game smooth.
* **Background Validation:** Every connected client independently runs a
physics raycast check on the incoming coordinates.
* **The Mesh Veto:** If a movement is mathematically impossible (e.g., the
distance traveled exceeds the maximum movement speed), the auditing peers
simply drop the packet.
* **Ghosting the Cheater:** The cheater's local screen will show them
successfully teleporting, but the rest of the mesh will completely ignore
them, rendering the cheat visually useless to everyone else.

By combining strict deterministic rules with floating zonal authority, you
create a self-healing, masterless physics simulation.

If a player assumes the "Room Host" role, how should we handle the exact
moment of handoff if they suddenly lose network connection mid-computation?