Roadmap
Each step ships when its example runs, its tests pass, and its costs are recorded against a control. The next one starts from that evidence.
Milestone 1 — the composition core
| Step | Proves | Status |
|---|---|---|
| 00 Pico | The facade costs nothing | Done |
| 01 Capability | Typed capability injection without Kernel | Done |
| 02 Module | Requirements resolved through Kernel | Done |
| 03 Contribution | Domain-owned targets assembled from modules | Prototype |
| 04 Process | Projection, configuration isolation, freeze, inspection | Prototype |
| 05 Lifecycle | Ordered start, readiness, drain and stop | In progress |
Also in this milestone: structured diagnostics, architecture tests and baseline measurements.
Deliberately out of scope for Milestone 1: HTTP, PostgreSQL, Redis, an ORM, MQTT, WebSockets, gRPC, real worker queues, a scheduler, AI, MCP, dynamic plugins, hot reload, a workflow engine, an admin UI, macros and a project generator.
After Milestone 1
In order, each depending on the one before:
- Full lifecycle
- Runtime abstraction proof
- Tokio runtime
- HTTP
- PostgreSQL
- Worker
- Deterministic loop
- Device
- Tooling —
clamp inspect,clamp why,clamp doctor - AI and MCP adapters
Release status
- No release yet. The changelog is entirely “Unreleased”; packages are
0.1.0withpublish = false. - crates.io: gated on a licensing decision and registry ownership.
- CI: checks run locally through
tools/check.py; hosted CI is not running yet.