Native application SDK
Cooperate with Semwright while keeping your application’s model, storage and transactions.
The Native SDK lets applications expose optional cooperation interfaces while remaining the source of truth for their own state. It adapts those contracts through the canonical Driver SDK and Driver Host. It does not add a second policy engine or a competing project store.
Choose the right integration level
Section titled “Choose the right integration level”| You own… | Start with… |
|---|---|
| An application model, revision scheme and transactions | Native SDK |
| A persistent provider around an existing application API | Application Driver SDK |
| A narrow, stateless external command | The product’s Plugin SDK |
| An agent that calls the runtime | CLI or MCP |
The Native SDK builds on the Driver SDK rather than replacing it.
Expose only the cooperation you need
Section titled “Expose only the cooperation you need”The Rust base has no default features. Applications can expose observations, operation contracts and recovery without adopting the SDK’s optional file-backed profiles. Scene, Table and Counter provide reference profiles; the TypeScript/SQLite inventory example demonstrates application-owned persistence and transactions.
Graph, Effects, packaging and the process bridge are separate opt-in features. The TypeScript binding provides bounded JSON values, opaque revisions, request/recovery helpers and the Host-mediated process bridge.
Authority remains with the host
Section titled “Authority remains with the host”Authority-bearing native operations use a DriverExecutionContext issued by Driver Host. Cooperation metadata, an application revision and an SDK object do not grant permissions. Broker policy, Project Graph and Effect Conformance keep their existing responsibilities.
Read the evidence at its original revision
Section titled “Read the evidence at its original revision”The SDK documentation records a canonical SDK/package baseline and Linux real-Host E2E at 09f71d490ac86f8f8e86dcda6c2552f50c59d487. Portable cooperation tests are recorded for Linux, Windows and macOS on x64/ARM64. Portable tests do not establish a real Host or interactive desktop certificate for every OS.
Start with the product’s minimal SDK quickstart, then read its API and authority contracts before implementing a provider.
Source: Native SDK overview and verification, source references checked 7 October 2026.