Rust platform
Proposed workspace & crate layout
An illustrative Cargo workspace showing how domain, service, UI and edge crates could relate.
Educational / conceptual specification · Not a released implementation contract
Illustrative workspace
PlannedThe layout below is a conceptual sketch for discussion. Names, boundaries and dependencies will change once implementation is public. It is not an installable project and there is nothing to clone today.
kaporeal/ # conceptual Cargo workspace
crates/
kp-domain/ # Load, Stop, Carrier, ShipmentEvent types
kp-lifecycle/ # state transitions + validation
kp-store/ # PostgreSQL persistence (SQLx, proposed)
kp-api/ # HTTP service core (Axum, proposed)
kp-events/ # outbox, subscriptions, provenance
kp-edi/ # X12 mapping research
kp-edge/ # no_std-friendly device protocol
apps/
dispatch-ui/ # Dioxus web + desktop
dock-tablet/ # Dioxus mobile
edge-gateway/ # embedded / ARM gatewayDependency direction
Domain crates depend on nothing operational. Storage, API and UI crates depend on the domain, never the other way around. Edge crates stay small enough to compile for constrained devices.