RECORDED EXECUTION

The workflow is simple.
The evidence is specific.

A real Rust project. A separately prepared environment. An execution container with networking disabled.

Rust + Docker · actual terminal recording22 SEP 2026 · LINUX ARM64
host$ docker compose run --rm prepare
 Network basecamp-terminal-recording3_default Creating 
 Network basecamp-terminal-recording3_default Created 
 Volume basecamp-terminal-recording3_project Creating 
 Volume basecamp-terminal-recording3_project Created 
 Container basecamp-terminal-recording3-prepare-run-b996f501ab44 Creating 
 Container basecamp-terminal-recording3-prepare-run-b996f501ab44 Created 
prepare$ basecamp sync
basecamp: downloading rust 1.95.0
install: creating uninstall script at /opt/basecamp/store/layers/toolchain/094c9c36531911c5cc7dd6ab2d3069ab8dcd744d6239b0bda1387b243dfc391e.partial-1/lib/rustlib/uninstall.sh
install: installing component 'rustc'
install: installing component 'rust-std-aarch64-unknown-linux-gnu'
install: installing component 'rust-docs'
install: installing component 'rust-docs-json-preview'
install: installing component 'cargo'
install: installing component 'rustfmt-preview'
install: installing component 'rust-analyzer-preview'
install: installing component 'llvm-tools-preview'
install: installing component 'clippy-preview'
install: installing component 'rust-analysis-aarch64-unknown-linux-gnu'
install: installing component 'llvm-bitcode-linker-preview'

    rust installed.

basecamp: syncing Cargo packages from the project's native Cargo sources
basecamp: environment ready · da057501da23 · Rust 1.95.0
host$ docker compose run --rm sandbox
 Container basecamp-terminal-recording3-sandbox-run-1884ea9f3fd5 Creating 
 Container basecamp-terminal-recording3-sandbox-run-1884ea9f3fd5 Created 
Docker container started. Network: none.
Project and Basecamp environment: mounted read-only.
sandbox$ 

sandbox$ cargo run --offline --locked

   Compiling itoa v1.0.15
    Building [                             ] 0/2: itoa                    
   Compiling sandbox-hello v0.1.0 (/workspace)
    Building [=============>               ] 1/2: sandbox-hello(bin)      
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.69s
     Running `/tmp/target/debug/sandbox-hello`
Hello from the offline sandbox. Answer: 42
sandbox$ cargo test --offline --locked

   Compiling sandbox-hello v0.1.0 (/workspace)
    Building [=============>               ] 1/2: sandbox-hello(bin test) 
    Finished `test` profile [unoptimized + debuginfo] target(s) in 0.32s
     Running unittests src/main.rs (/tmp/target/debug/deps/sandbox_hello-cea6939fc146fdf3)

running 2 tests
test tests::formats_answer ... ok
test tests::runs_without_a_network_dependency ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

sandbox$ ls /sys/class/net

bonding_masters  gre0	  ip6_vti0  ip6tnl0  lo    tunl0
erspan0		 gretap0  ip6gre0   ip_vti0  sit0
sandbox$ exit

exit
host$ exit
exit

This is a recording, not a command runner. Display duration: 28.93 seconds; original: 73.63 seconds. Idle gaps were compressed, output was preserved. Playback does not measure cold preparation performance.

WHAT WAS RECORDED

Two containers.
Different responsibilities.

The preparation service runs basecamp sync with the required bootstrap Rust and system tools. A different execution image has Rust and Cargo removed from PATH before the prepared environment is activated.

The task then runs Cargo offline in a network-disabled container. The application prints its result and two tests pass.

WHAT THIS DOES NOT PROVE

One configuration.
Not every combination.

The fixture uses Linux arm64 and a cached official distribution archive. It does not certify all languages, all targets, cold-download speed, or arbitrary private AI sandboxes.

Inspect the source, metadata and receipt. Keep the preparation model separate from its specific implementation evidence.

Read the no-target-install acceptance contract