Remote / foldkit-remote

Boundaries: what Remote manages vs. your app

Remote manages:

  • typed entity identity, references, selections, and patches;
  • the normalized entity store, field presence/staleness, and tombstones;
  • pure requirements and deterministic planning;
  • the Remote.Model Submodel and its reducer;
  • query connections and pagination boundaries;
  • optimistic mutation overlays and idempotent settlement bookkeeping;
  • the outbox of durable writes: stored, sent in order by one tab, sent again;
  • live cursors, duplicate suppression, and gap detection;
  • retention/garbage collection of disposable cache data;
  • deterministic, scoped cache snapshots;
  • the RemoteClient semantic transport seam and RemoteRpc schemas;
  • pure introspection of the cache and plans.

Your application and neighbouring packages manage the rest: your source database and server records belong to your server Sources (foldkit-remote-server), local UI state outside Remote.Model belongs to your Model and update, offline client-authored convergence belongs to foldkit-sync, and HTTP/WebSocket transport and authentication belong to your RPC/HTTP layers.