System One SDK Poncho

Four independently publishable Mix projects. This repository is a Poncho, not an Elixir umbrella: each package owns its dependencies, lockfile and build. The root provides documentation and orchestration only.

Package	Purpose	Typical user
system_one_contracts	Small provider-neutral System One v1 wire/inference contract package	Runtime/server implementers
system_one_sdk	Rich provider-neutral System One API and default hosted TypeSafe integration	Nearly everyone
system_one_bumblebee	Optional native BEAM/Nx model execution (upcoming)	Self-hosted/native inference users
system_one_server	Optional HTTP service exposing System One v1 (upcoming)	Remote/service deployments

Most application users need only:

{:system_one_sdk, "~> 0.6"}

Runtime/server implementers may depend directly on the smaller system_one_contracts package. The SDK 0.6.0 and contracts 0.1.0 lines are under development; SystemOneSDK 0.5.0 and TypeSafeAPISDK 0.1.0 are published.

SystemOneSDK itself is programmatic. The server is optional. Native inference is optional. Hosted use does not require Bumblebee, Nx, EXLA, Plug or Bandit. The provider-specific typesafe_api_sdk remains an ordinary Hex dependency of the main SDK.

Development

./scripts/qc
cd packages/system_one_sdk
mix docs --warnings-as-errors

Fast QC fetches dependencies and runs formatting, test compilation and offline tests per package. It does not run live calls, Dialyzer or model downloads. During development the SDK, Bumblebee and Server use explicit sibling path dependencies on system_one_contracts; release gates reject those path dependencies until the contracts package is published and the dependency is switched to {:system_one_contracts, "~> 0.1.0"}.

See architecture, packages, roadmap, release order, verification and publishing.

MIT License — Copyright (c) 2026 nshkrdotcom