Queues + KV · protocol prototype

Both clients execute the same Rust WASM module as the Worker. Queue acceptance keeps an operation pending; observing its immutable KV record confirms custody. Opaque intents below demonstrate transport, not Inventory reconciliation.

Journal: . Share this link to observe the same journal on another device.

Loading WASM…

Try the failure cases

  1. Prepare an intent on A; it is persisted locally before it can be sent.
  2. Enqueue pending work. The event remains pending.
  3. Poll B and A to observe retained events and reconcile custody.
  4. Return a stale empty response or restart a client: known events remain.
  5. Replay pending work or deliver a duplicate: there is still one event.
Runtime capacity: 128 events per client, 4 KiB per intent. This demo preserves all event history; it does not claim instant cross-device deletion or server freshness.