Skip to main content
rusty separates immutable content (the store) from compiled outputs (layers and artifact cache). That split is what makes large monorepos reuse work across packages and machines with the same inputs.

Content store (CAS)

pnpm-style content-addressable storage under $RUSTY_HOME:
Trees and crates:
Fetch pipelines ingest registry crates into the store, then materialize views for the compiler as needed. Integrity of store contents is security-critical — treat digests as the source of truth.

Build layers

Per-crate differential cache in the project .rusty/ directory:
Use plan before a large build to see what should rebuild.

Artifact cache

Compiled artifact groups, including wrapper integration:
During normal builds, rusty sets RUSTC_WRAPPER to rusty-wrapper so rustc invocations participate in the layer/artifact machinery.

Project target directory

Compiled outputs for the workspace go under:
rusty clean removes that tree. This is also the CARGO_TARGET_DIR rusty injects for interop-compatible environments.

Environment toggles

See Environment.