What Tilo is, and why

Most collaboration tools are honest about one limitation: when two people edit the same thing at the same time, somebody's change gets dropped. Tilo is built around the opposite premise. Every edit survives. The merge is deterministic. Every device sees the same state.

Underneath the canvas is a from-scratch CRDT engine written in Rust. It implements three classical primitives (Lamport clocks, last-writer-wins registers, observed-remove sets) with a semantic-resolution layer on top that enforces domain rules after convergence. The convergence property is verified by 8000+ randomised tests on every commit.

The interesting part is what the engine enables. Two people on the same WiFi can collaborate without a server in the middle. Three offline tabs can edit the same canvas for a week, and when they reconnect, every edit lands in the right place. The same engine could power shared budgets, multiplayer board games, or inventory systems where double-booking is impossible.

The canvas is the demo. The engine is the product.