Project inputs
The CLI fingerprints environment-relevant project inputs locally and sends their SHA-256 identities to the Rust resolver. Cargo.toml, Cargo.lock, rust-toolchain files, and native Cargo configuration are not uploaded as a remote build workspace on the normal Rust path.
Verified sources
Direct binary sources are locked by SHA-256. Registry layers are tied to the native ecosystem lock digest. Basecamp validates project input digests before synchronizing an existing lock.
Local isolation
Basecamp keeps shared immutable layers in its own store and generates project-specific activation state. For Cargo, an activation shim forces the Basecamp source configuration so host Cargo mirrors or global configuration cannot silently change the synchronized environment. Basecamp rejects Cargo config files found above the project root; required source/build settings must live in the project's .cargo directory.
Optional CAS
Trusted infrastructure can publish verified content-addressed layers for controlled or prebuilt inputs. The v0.5 control plane does not accept arbitrary project execution jobs or schedule remote builders.
Air-gap
Bundles carry the exact lock and materialized layers needed to restore the environment without network access.