Offline Protocol glossary - Offline Protocol

Term	Definition
Acceptance	A receiver’s explicit decision to commit or take responsibility for an operation.
Adapter	Code translating a source record into a destination’s schema and commit contract.
Address	Key-derived `off1…` device identifier.
App ID	Public `app_…` identifier of an application in the developer portal, sent as `x-app-id`. OfflineID and Proof of Location require it. It is not a secret.
CRDT	A replicated data structure with deterministic merge rules for concurrent edits.
DORS	Dynamic Offline Relay Switch, the SDK’s transport-selection mechanism.
Full peer	A deployment running the protocol functions needed for session management and coordination.
Hosted relay	Offline Protocol’s hosted internet relay, which carries messages between peers over WebSocket when a device has an internet connection. Messages it carries are metered as hosted relay deliveries.
Leaf	A constrained MLS member relying on a full peer for commits.
Mesh app identifier	The `appId` string passed to the Mesh SDK’s `OfflineProtocol` constructor. You choose it; with the profile, it scopes local storage. It is not the portal App ID.
MLS	Messaging Layer Security, used for encrypted sessions and groups.
OfflineID	Offline Protocol’s hosted account identity service: email sign-in, usernames, profiles and connections. It is separate from a device’s mesh address.
Outbox	Retained pending work, bounded by capacity and lifetime.
Profile	Local selector for an application’s identity and storage namespace.
Reconciliation	Comparing retained local work with destination acceptance and completing missing work.
Service	An advertised application operation with an ID, version and metadata.
Space	Session or group scope for shared documents.

See core concepts for how these fit together.