Platform SDK overview
Build independent applications with application-owned data, authority, and peer communication.
Build an independent application with your own data model and authority policy. Platform provides local storage, replication, events, live streams, and peer communication.
Choose the data path
| Requirement | Mechanism | Completion means |
|---|---|---|
| Retain a report or latest saved observation | Schema-backed record or document | A local commit, followed independently by replication |
| Announce a bounded fact | Event | Local acceptance, with a separate delivery outcome |
| Receive continuing producer samples | Live stream | An authorized, consumer-owned subscription |
| Exchange protocol-specific bytes | Managed transport or messaging | The selected protocol's delivery result |
| Derive allowed state transitions | Workflow | A validated transition and derived state |
A local UI notification does not confirm remote event delivery. A stream descriptor describes a stream but does not open a subscription. A schema defines data but does not create storage or a transport.
Choose a primitive
| Topic | Model |
|---|---|
| Entities | Track, Geo, Asset, and Template values, including relationships and derived quantities |
| Groups | Proof-carrying membership with offline conflict resolution |
| Schemas | Field definitions, validation, and merge semantics |
| Documents | Schema-bound structured fields and lifecycle |
| Blobs | Content-addressed binary references |
| Events | Bounded notification envelopes and delivery outcomes |
| Streams | Producer descriptors and continuing samples |
| Workflows | Transition definitions and derived state |
The Entity primitive is distinct from a generic record's EntityRef. Records belong to the storage interface.
Principal belongs to Identity. Capability delegation belongs to Authorization. Their Principal and Authorization references remain separate from the eight primitive topics above.
Keep application ownership explicit
You choose record types, schema versions, replication scopes, capability commands, trusted roots, and external adapters. A replication scope names the data peers exchange. A capability authorizes an action on that data. Matching scope names do not grant access.
Two independent peers can exchange your records directly. You can run an always-on peer for availability without changing the application's data model or authority.
Platform also provides identity and authorization, messaging, and logging. Read those concepts as your task needs them.
Select a reference
Language references describe exact declarations and target constraints. Use Rust for custom composition, Python for native integrations, Kotlin, Swift, browser TypeScript, or Dart.
Read compatibility before pairing packages, changing schemas, or deploying mixed peer versions.