Rust, gently
A field guide for orchestrators
A field guide, not a manual

Rust,
gently.

A field guide to Rust for builders whose agents write most of the code. Twenty chapters, rebuilt from The Rust Book, retold through the orchestrator's lens, grounded in real snippets from a production query engine.

Open the book →Why Rust mattersOrchestrator playbookSail tour
Field signalsSee the lexicon →
  • No GC

    Peak performance at request one. No warmup, no garbage collector to tune.

  • Send and Sync

    Data races become compile errors. Concurrency is a type check, not a code review item.

  • Arrow columnar

    Engines share record batches across processes and languages without copying bytes.

Four tracks, one mission.

Read in any order
Track I
The Book

The full Rust Book retold for orchestrators. Twenty chapters from getting started to a hand-built web server, each one threaded with what to grep for in agent-written code.

20 chapters · 4 hrs→
Track II
Orchestrator playbook

The operational manual. Twelve failure modes, the cargo gates, prompting templates that work, a five-minute PR review playbook, the compiler-error decoder.

6 chapters→
Track III
Concept distillations

The fast paths through the same material as the book. Open one when you want the answer now: ownership, errors, traits, async, the five questions for any Rust file.

11 distillations→
Track IV
Ecosystem + Sail tour

Where Rust matters: query engines, AI inference, agent infra, web/systems. Then a real tour through the Sail codebase — 36 crates, one query engine, every concept in production.

9 chapters→

If you only have one evening.

The minimum viable path to start reviewing agent-written Rust by tomorrow.

  1. i
    Get the shape

    Where Rust code lives, how it compiles, why people write it.

  2. ii
    Read ownership

    The thing the borrow checker is asking about. Most agent-written bugs live here.

  3. iii
    Read error handling

    The other half of agent-written bugs.

  4. iv
    See the failure modes

    Twelve concrete patterns to grep for in any Rust diff.

  5. v
    Install the gates

    Make the agent prove correctness instead of arguing about it.

  6. vi
    Run the playbook

    Five questions, five minutes, every PR.

◇ What this is
  • A handbook for orchestrators of agent-written Rust.
  • The classic Rust Book reframed for the workflow most builders actually have.
  • Sail-biased examples from a real Rust query engine.
  • Aggressively short. Every section earns its place.
△ What this is not
  • A reference for hand-writing production Rust from scratch.
  • An advanced systems-programming text.
  • Comprehensive. It is a filter, not a firehose.
  • A replacement for the original Rust Book, which you should also read.