Runtime Planned
Kernel decides what runs. Runtime is what actually runs it — a thread, an async executor, a deterministic loop. Keeping them apart is why a tiny tool never pulls in an async runtime.
Status. The rustclamp-runtime repository exists as an empty scaffold with no public contracts. Everything on this page is design direction, not API.
Why a separate layer
- Zero-cost absence. No async code means no async runtime requirement. No I/O loop means no I/O machinery.
- Many kinds of software. A CLI, a network service, a game loop and a device firmware loop execute differently. The composition model should not change between them.
- Abstractions over products. Modules should require an execution ability (an async runtime), not a specific crate. Tokio can then be one provider rather than a framework assumption.
Responsibilities, as designed
| Kernel | Runtime |
|---|---|
| Resolves and freezes what a process contains | Drives execution of that frozen plan |
| Orders lifecycle participants | Provides the scheduling those participants run on |
| Coordinates | Executes |
Roadmap position
After the lifecycle work: first a runtime abstraction proof, then a Tokio-backed runtime, then a deterministic loop. See Roadmap. Today, the only execution model is the facade's: Clamp::run calls your closure once on the current thread.