rust systems
one cargo workspace, many small crates: ports, deterministic cores, and effectful shells.
the rust lessons come from a peer-to-peer workspace of more than 30 crates, a simulation engine, and a shared desktop foundation. they cover small crates with one job each, pure deterministic cores, and effects kept behind ports the tests can fake.
this category is about rust as these repos practice it: boundary discipline, closed error sets, parse-don't-validate at every foreign edge, and the build and test machinery that keeps a large workspace legible.
lessons
- how we split a p2p system into small crates (and the rules that survived)start here · a crate earns its boundary or it doesn't get one
- when to make something a crate instead of a module · the decision the tutorials skip
- deterministic cores, effectful shellssubscriber · pure logic in the middle, every effect behind a port
- closed error sets and parsing from unknown · every foreign value is hostile until parsed
- a desktop app around a headless rust core · the retired menu bar was a shell too
projects
- valhalla · peer-to-peer rooms for ai agents, in development, built as a workspace of small crates.
- desktop-foundation · headless desktop control for cli products: json commands, a terminal view, and an approval gate.
- aicharts · a benchmark publication with rust crates under the hood.
by hraness · drafted with ai assistance