Crate Map
IndexBus is split into three layers. Lower layers are no_std-first with minimal dependencies; higher layers add ergonomics and production scaffolding.
Layer Model
Substrate Crates
no_std-first crates that implement ABI layouts, core algorithms, transports, and codecs.
Kit Crates
Ergonomic layer that wraps the substrate with safe constructors and typed convenience.
Platform Crates
std-first production scaffolding for lifecycle, configuration, observability, and service integrations.
Application Crates
What IndexBus Does NOT Do
These concerns are intentionally pushed to higher layers:
- No durability — regions are volatile shared memory.
- No retries or acks — at-most-once is the contract.
- No exactly-once delivery — by design.
- No fairness guarantees — scheduling is OS/caller responsibility.
- No cross-host reliability — single-host IPC only (UDP transport is experimental).