Crate solti 

solti

Feature and namespace façade for the modular Solti SDK. It contains no runtime logic. Features select component crates and expose them under stable namespaces.

Use this crate when an agent binary needs several SDK components. Depend on a component crate directly when one component is enough.

Start Here

1. Choose the capabilities required by the binary.
2. Enable their solti features.
3. Import each component through its namespace.
4. Build and own the application runtime.

All features are disabled by default. Higher-level features enable their required lower layers.

Feature Flow

application features
         ▼
       solti
         ├── model ─────────────► solti-model + JSON Schema
         ├── runner ────────────► solti-runner + model + taskvisor
         ├── core ──────────────► solti-core + runner + taskvisor/controller
         ├── exec-* ────────────► solti-exec integrations
         ├── api-* ─────────────► solti-api transports and adapters
         ├── discover-* ────────► solti-discover transports
         ├── observe-* ─────────► solti-observe integrations
         ├── prometheus-* ──────► solti-prometheus integrations
         └── tls ───────────────► solti-tls

Component crates never depend on this façade. The façade preserves their ownership boundaries.

Choose Features

Need	Feature family
Resource types and schemas	model
Runner registration	runner
Desired-state supervision	core
Host process controls	exec-host-process
Subprocess execution	exec-subprocess
Container engine boundary	exec-container
Native containerd 2.x	exec-containerd
Seccomp host process filter	exec-seccomp
HTTP task API	api-http
gRPC task API	api-grpc
Core API adapter	api-core-adapter
gRPC server TLS	api-grpc-tls
HTTP discovery	discover-http
gRPC discovery	discover-grpc
Discovery TLS	discover-tls
Logging integrations	observe-*
Prometheus integrations	prometheus-*
Shared TLS types	tls
Taskvisor integrations	taskvisor-*

exec-seccomp enables the low-level host process filter. Combine it with exec-subprocess to filter subprocess attempts. exec-container exposes the engine-neutral container runner. exec-containerd adds the native containerd 2.x adapter.

api-http and api-grpc expose transports. They do not enable solti-core. Add api-core-adapter when the API delegates to core::SupervisorApi.

discover-http and discover-grpc select the outbound discovery transport. They do not select the task API exposed by the agent.

model includes the solti-model/schema feature. The full feature enables the complete standard integration set.

Namespaces

Namespace	Component crate
api	solti-api
core	solti-core
discover	solti-discover
exec	solti-exec
model	solti-model
observe	solti-observe
prometheus	solti-prometheus
runner	solti-runner
taskvisor	taskvisor
tls	solti-tls

A namespace exists only when its owning feature is enabled. Re-exported APIs keep their component-crate paths below that namespace.

Quick Start

Enable only the components used by the binary:

[dependencies]
solti = { version = "0.0.3", features = [
    "api-core-adapter",
    "api-http",
    "exec-subprocess",
] }

Use the canonical namespaces:

use solti::core::SupervisorApi;
use solti::exec::subprocess::register_subprocess_runner;
use solti::runner::RunnerRouter;

let mut router = RunnerRouter::new();
register_subprocess_runner(&mut router, "default")?;

let supervisor = SupervisorApi::builder(router).start().await?;

Re-exports

pub use solti_api as api;api

pub use solti_core as core;core

pub use solti_discover as discover;discover

pub use solti_exec as exec;exec

pub use solti_model as model;model

pub use solti_observe as observe;observe

pub use solti_prometheus as prometheus;prometheus-base

pub use solti_runner as runner;runner

pub use taskvisor;taskvisor

pub use solti_tls as tls;tls