BACKED — a peer-to-peer group scheduling tool where people back the times they’ll actually protect, instead of checking every box they’re technically free for. A scarce commitment budget forces real preferences to surface, and the room locks automatically once one option becomes mathematically unbeatable.

The starting repo depended on a competitor’s deployed Cloudflare Worker, so simply remixing the UI would have left us coupled to their infrastructure. I removed that backend and rebuilt multiplayer around WebRTC with a host-authoritative room model. The bigger product challenge was making the remix meaningfully different instead of producing a reskin. We replaced ordinary availability voting with a scarce commitment budget, added conflict states, automatic backing retraction, room purpose, deterministic tie handling, and an “inevitable winner” rule where a decision locks once the leader is mathematically uncatchable. I also separated the decision logic into a testable client-side core. The core scheduling tests pass, including budget limits, conflicts, automatic locking, ties, and conflict-triggered backing removal. The remaining WebRTC constraint is peer discovery: browsers cannot discover arbitrary peers on the internet with WebRTC alone, so PeerJS signaling is used only to establish connections while room data travels peer-to-peer.