Mesh status
…
Peers connected
—
Room key
—
Enable mesh sync on this device
◆ First-time setup
Pick one option below:
I am the first device
Generate a new room key. Chrissy runs this on her primary device (phone or laptop) once, then shares the key with Marius and other trusted staff via QR code (below).
I am joining an existing mesh
Paste the room key Chrissy has shared with you, or scan her QR code from another device.
◆ Trust model · read this once
- Anyone with the room key becomes a peer. Peers see all shared state (bookings, messages, notes). Only share with people Chrissy trusts to represent Wishwood.
- Peer discovery uses BitTorrent trackers. Trackers only see a random room hash, never the room key contents. Data channels themselves are direct browser-to-browser (WebRTC), encrypted in transit.
- If a staff member leaves · generate a new room key on Chrissy's device, share with the remaining team. The old key becomes orphan · the former staff device just sees "no peers".
- Offline is fine. Each device keeps its own copy of state in IndexedDB. Changes made offline sync when the device rejoins the mesh.
- This layer is separate from the Cloudflare Worker — the hub still uses the Worker for Stripe, webhooks, cron. But the day-to-day operator view syncs peer-to-peer, no server needed.