Architecture
Who this section is for. Contributors to the source repository and platform engineers deploying the stack. It assumes familiarity with Rust workspaces and container orchestration.
Available now
Analysis flow, data ownership per crate, interface differences, time and frame handling.
Crate boundariesTwenty-one crates, how they layer, and why four capabilities are reachable only through the API.
API architectureIn-memory state, a three-code error model, and the limits that decide which measurements can be made over HTTP.
Decision recordsArchitectural decisions and their consequences, recorded rather than remembered.
What these pages are read from
Both new pages are derived from the source rather than from description: the
crate graph from the Cargo.toml files, the route table and limits from the API
crate itself.
That matters because the source repository’s own architecture note predates
several shipped capabilities. Reconciling against the current crate list and
route table was a precondition for publishing, and it surfaced things the note
does not mention, including that econ, replan, resilience, and trade have
no CLI entry point at all.
Not yet published
Simulation data flow, web UI architecture, deployment across Docker, Compose, Kubernetes and Envoy, observability, coding standards, contributing, and the roadmap.
main (pre-release)