Skip to main content

Rust Runtime Guide

Rust is a Tier 1 TeaQL runtime for native services, explicit provider composition, and small deployable artifacts. It implements the same generated Q, E, Mutation, context, audit, Checker/Fix, Runtime Module, and explicit Ensure Schema contract as the other six runtimes.

Start here​

  1. Rust Quick Start — evaluate a model and generate the current Rust workspace.
  2. Rust First Verification — verify build, SQLite execution, intent, audit, and regeneration.
  3. Rust Business Scenarios — move from expressions and transactions to provider-backed application flows.
  4. Rust Customization — compose context, providers, policy, telemetry, and deployment boundaries.
  5. Rust Debugging and Observability — inspect safe SQL evidence, traces, mutation audit, telemetry, and tenant policy.

The detailed Rust Runtime Overview explains crate and provider architecture. Use Latest Versions for coordinates and Cross-language Conformance Status for shared capability evidence.

Evidence boundary​

Rust has dated native and provider evidence, but release discovery, generated dependency selection, capability evidence, and support lifecycle are different claims. Use the Verification Evidence archive for older campaigns and re-run the First Verification against the generated workspace and provider combination you intend to ship.

Learn through an Order​

Follow the Order tutorial to download the first-flow source package, build with Rust 1.97.1 and locked public TeaQL 5.0.7 crates, initialize SQLite and complete the first read/edit/readback. Later page/advanced recipes keep their workspace and pending-release requirements. Use the Order API usage guide for result shapes and the native troubleshooting table for recovery. The coverage matrix keeps remaining writing and clean-machine packaging gaps visible. Existing runtime pending-release and generator-deployment qualifications remain in place.

Understand partial entity loading​

Read Rust ORM partial loading: SQL NULL vs NotLoaded for the query-completeness problem, then use the native tutorial and debugging path above. For query authoring, compare generated APIs with handwritten SQL.