Crates and packages

Every published origin-* crate and npm package, grouped by layer, with links to crates.io, docs.rs and npm.

All 29 crates and both npm packages share the workspace version, currently 0.2.0. Item-level API documentation lives on docs.rs; this page is the map. How the layers depend on each other is described in the architecture overview.

Contracts

Crate	Purpose	Links
`origin-domain`	Origin domain primitives and platform ports. Knows no product, no Tauri, no storage engine.	crates.io · docs.rs
`origin-platform`	Platform contracts for Origin: the OS capabilities domain code is allowed to depend on.	crates.io · docs.rs

Platform

Crate	Purpose	Links
`origin-events`	Typed, in-process event bus for Origin. No string topics, no untyped payloads.	crates.io · docs.rs
`origin-secrets`	SecretStore contract for Origin, with an in-memory implementation and a shared contract test suite.	crates.io · docs.rs
`origin-settings`	Typed user settings for Origin, backed by any Storage implementation.	crates.io · docs.rs
`origin-storage`	Storage port and TTL cache for Origin. Knows no storage engine.	crates.io · docs.rs
`origin-http`	HTTP port for Origin: request and response types, rate-limit parsing, status mapping. Knows no HTTP library.	crates.io · docs.rs
`origin-auth`	OAuth 2.0 authorization code flow with PKCE, token storage and refresh for Origin.	crates.io · docs.rs
`origin-accounts`	Account management for Origin: several accounts per connector, credentials kept out of the database.	crates.io · docs.rs
`origin-connector`	The connector contract for Origin: what an external service integration must declare and support.	crates.io · docs.rs
`origin-sync`	The Origin sync engine: scheduling, backoff, offline handling and sync state. Knows no external service.	crates.io · docs.rs
`origin-jobs`	Background jobs for Origin: progress, cancellation and a uniform lifecycle.	crates.io · docs.rs
`origin-mcp-core`	The MCP boundary: which of an application’s operations an external AI may invoke, and under which permission.	crates.io · docs.rs
`origin-ai`	The AI port for Origin: inference the application performs itself, behind a swappable adapter.	crates.io · docs.rs
`origin-telemetry`	Tracing setup and logging conventions for Origin.	crates.io · docs.rs
`origin-app`	Composition root machinery for Origin applications: ApplicationBuilder, modules, service registry.	crates.io · docs.rs

Tooling

Crate	Purpose	Links
`origin-manifest`	The Origin app manifest: what a product is, parsed and validated.	crates.io · docs.rs
`origin-xtask`	Origin maintenance tasks as a library, so a derivative’s xtask is three lines and its rules arrive with a version bump.	crates.io · docs.rs

Adapters

Crate	Purpose	Links
`origin-storage-sqlite`	SQLite-backed Storage adapter for Origin.	crates.io · docs.rs
`origin-secrets-system`	SecretStore adapter backed by the operating system credential store.	crates.io · docs.rs
`origin-http-reqwest`	HttpClient adapter backed by reqwest.	crates.io · docs.rs
`origin-auth-loopback`	Loopback redirect listener for the OAuth authorization code flow (RFC 8252).	crates.io · docs.rs
`origin-mcp-stdio`	MCP over stdio: the transport a desktop AI client uses to start an application headless.	crates.io · docs.rs
`origin-mcp-http`	MCP over a local loopback HTTP endpoint: the transport a desktop AI client uses to reach an already-running GUI instance.	crates.io · docs.rs
`origin-process-std`	ProcessRunner over the local machine: start allowlisted programs and read their output.	crates.io · docs.rs
`origin-workspace-fs`	WorkspaceFs over the local filesystem: read-only access under user-confirmed roots.	crates.io · docs.rs
`origin-workspace-watch`	WorkspaceWatcher over the notify crate: event-driven local sync for working-tree changes.	crates.io · docs.rs
`origin-notifications-tauri`	NotificationService adapter backed by tauri-plugin-notification.	crates.io · docs.rs

Host

Crate	Purpose	Links
`origin-tauri`	Tauri host layer for Origin: plugin wiring, tray, IPC commands and the event bridge.	crates.io · docs.rs

Frontend packages

Package	Purpose	Links
`@casoon/origin-client`	The only package that speaks Tauri IPC: typed commands, platform events and generated types.	npm
`@casoon/origin-ui`	Shared Svelte 5 components and design tokens.	npm

Not published

origin-demo (examples/demo/src-tauri) — the reference application.
xtask — the repository’s own cargo xtask entry point; the tasks live in origin-xtask.

The publishing order and procedure are in Publishing.

Edit this page on GitHub · Docs for v0.2.0