forge docs

Rust Tools

This page shows Tools from the Rust SDK perspective. The shared Forge contract still applies, but examples, package boundaries, verification commands, and deployment expectations should be read through reference runtime, conformance, WASM, deterministic crypto, and low-level production behavior.

Language context

  • Primary package surface: forge-rs
  • Install entry point: cargo add forge-sdk
  • Verification command: cargo test --workspace
  • Shared contract reference: Tools

Rust is the contract anchor. When behavior is ambiguous, start here and compare other SDKs against the conformance fixtures.

Subject in Rust

For Rust, focus on tool tiering, approval policy, typed arguments, runtime errors, and audit evidence. Treat this page as the language-specific entry point, then use the shared contract page when you need the cross-language rule text.

Implementation checklist

  1. Start with the Rust package boundary rather than copying examples from another SDK.
  2. Keep OAS identity and Arsenal capability checks visible in the code path.
  3. Use provider names through Forge's namespace contract instead of hard-coding vendors.
  4. Run cargo test --workspace before claiming behavior is ready.
  5. Run python3 tools/release_gate.py --root . before release work.
cargo add forge-sdk
cargo test --workspace