Capability map#
What you use day to day — product surfaces, not an inventory of private implementation modules.
Authoring#
| Surface | What you use it for |
|---|
| Bindles | Pack the app: services, resources, wiring, policy intent |
| App Kits | Entrypoint kinds (api, web, service, …) inside a Bindle |
| Camps / Yards / Junctions | Topology: home, provider scope, federation |
| Trails | Continuous migration recipes + live upgrade/migration executors (preflight evidence, expand→backfill→contract, pooled→siloed tenant moves) |
Runtime (Camp)#
| Surface | What you use it for |
|---|
| EventStore | Append-only domain and control facts |
| Queue / messaging | Deferred work and pub/sub |
| Streamer | High-volume frames (logs, tokens) |
| ActorHost | Single-writer leases and fencing |
| Clock | Deterministic time for workflows and tests |
| Session Replay | Privacy-first session capture on App Kits |
Default durable journal is a single-owner SQLite path. Alternate engines and component hosts (Wasmtime, OCI/Kubernetes, cloud-native) plug in behind the same ports.
Control & identity#
| Surface | What you use it for |
|---|
| Stations & Conductor | Control-plane isolation + placement decisions; routing control loop + progressive cutover |
| Dispatcher | Deterministic credit/budget-aware backend selection (dispatch.Decided) |
| Jurisdiction & residency | Region→jurisdiction catalog, per-tenant residency constraints, fail-closed residency gate |
| Gatekeeper / contracts | can-deploy and composed deploy gates |
| Policy packs | Deny-by-default authorization and obligations |
| Identity | Workload identity, brokered tokens, continuous identity |
| Harness | Flags, progressive delivery, experiments |
| Connectivity | Named endpoints, overlay, secretless connectors |
Operator surfaces#
| Surface | What you use it for |
|---|
hobo CLI | Lifecycle, diagnosis, authoring, ops |
| MCP | Same verbs for agents |
| Metering | Usage facts and showback |
Rules of thumb#
- Author Bindles and topology — not storage engines.
- Talk to ports (EventStore, Queue, Messaging); engines stay swappable.
- Prefer secretless federation over long-lived keys.
- Conformance is what “certified provider” means — same bar for every adapter.
Architecture · Component hosts · Runtime ports · CLI